aboutsummaryrefslogtreecommitdiff
path: root/COPYING.NEWLIB
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@suse.com>2022-03-21 15:13:35 +0100
committerJan Beulich <jbeulich@suse.com>2022-03-21 15:13:35 +0100
commit46fb6d5aa27d7129f472729a4f7ab8aa103aa674 (patch)
tree4a08cc0a23186e11ecc4132979ea558f2fc36f8b /COPYING.NEWLIB
parent4b19214f7920a4dbb7acf42a4da667600d23bd6a (diff)
downloadfsf-binutils-gdb-46fb6d5aa27d7129f472729a4f7ab8aa103aa674.zip
fsf-binutils-gdb-46fb6d5aa27d7129f472729a4f7ab8aa103aa674.tar.gz
fsf-binutils-gdb-46fb6d5aa27d7129f472729a4f7ab8aa103aa674.tar.bz2
x86: don't suppress overflow diagnostics in x32 mode
Unlike in 64-bit mode, where values wrap at the 64-bit boundary anyway, there's no wrapping at the 32-bit boundary here, and hence overflow detection shouldn't be suppressed just because rela relocations are going to be used. The extra check against NO_RELOC is actually a result of an ilp32 test otherwise failing. But thinking about it, reporting overflows for not-really-relocations (typically because of earlier errors) makes little sense in general. Perhaps this should even be extended to non- 64-bit modes.
Diffstat (limited to 'COPYING.NEWLIB')
0 files changed, 0 insertions, 0 deletions