signal: Add FPE_FLTUNK si_code for undiagnosable fp exceptions
Some architectures cannot always report accurately what kind of floating-point exception triggered a floating-point exception trap. This can occur with fp exceptions occurring on lanes in a vector instruction on arm64 for example. Rather than have every architecture come up with its own way of describing such a condition, this patch adds a common FPE_FLTUNK si_code value to report that an fp exception caused a trap but we cannot be certain which kind of fp exception it was. Signed-off-by: Dave Martin <Dave.Martin@arm.com> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
This commit is contained in:
parent
f6a015498d
commit
266da65e91
|
@ -26,7 +26,7 @@ static inline void signal_compat_build_tests(void)
|
||||||
* new fields are handled in copy_siginfo_to_user32()!
|
* new fields are handled in copy_siginfo_to_user32()!
|
||||||
*/
|
*/
|
||||||
BUILD_BUG_ON(NSIGILL != 11);
|
BUILD_BUG_ON(NSIGILL != 11);
|
||||||
BUILD_BUG_ON(NSIGFPE != 13);
|
BUILD_BUG_ON(NSIGFPE != 14);
|
||||||
BUILD_BUG_ON(NSIGSEGV != 4);
|
BUILD_BUG_ON(NSIGSEGV != 4);
|
||||||
BUILD_BUG_ON(NSIGBUS != 5);
|
BUILD_BUG_ON(NSIGBUS != 5);
|
||||||
BUILD_BUG_ON(NSIGTRAP != 4);
|
BUILD_BUG_ON(NSIGTRAP != 4);
|
||||||
|
|
|
@ -229,7 +229,8 @@ typedef struct siginfo {
|
||||||
# define __FPE_INVASC 12 /* invalid ASCII digit */
|
# define __FPE_INVASC 12 /* invalid ASCII digit */
|
||||||
# define __FPE_INVDEC 13 /* invalid decimal digit */
|
# define __FPE_INVDEC 13 /* invalid decimal digit */
|
||||||
#endif
|
#endif
|
||||||
#define NSIGFPE 13
|
#define FPE_FLTUNK 14 /* undiagnosed floating-point exception */
|
||||||
|
#define NSIGFPE 14
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* SIGSEGV si_codes
|
* SIGSEGV si_codes
|
||||||
|
|
Loading…
Reference in New Issue