[Bug binutils/24064] bfd/warning.m4 warning detection broken when !defined(__GNUC__)
https://sourceware.org/bugzilla/show_bug.cgi?id=24064 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Alan Modra --- Patch applied, thanks! -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/24044] FTB with GCC libiberty: binutils/stabs.c:3042: undefined reference to `cplus_mangle_opname'
https://sourceware.org/bugzilla/show_bug.cgi?id=24044 --- Comment #7 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=236f4ebe3ac7e8f94184fdcc39c70d74cc62b82a commit 236f4ebe3ac7e8f94184fdcc39c70d74cc62b82a Author: Nick Clifton Date: Tue Jan 8 16:53:02 2019 + Remove support for old gnu v2 name mangling. PR 24044 * cxxfilt.c (hp_symbol_characters): Delete. (main): Remove depcreated demangling styles. * stabs.c (parse_stab_argtypes): Remove support for old gnu v2 demangling opnames. * testsuite/binutils-all/cxxfilt.exp: Use the --no-strip-underscore option for targets that do prefix their symbols with underscores. Update tests to elimiate those that use gnu v2 encoding. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/24065] 32-bit objcopy fails with '64-bit address ... out of range ...'
https://sourceware.org/bugzilla/show_bug.cgi?id=24065 --- Comment #5 from Liviu Ionescu --- Thank you, Christina, thank you, Alan. Since the GNU MCU Eclipse GCC distribution usually follows the Arm distributions, I'll talk to them and, depending on their release plans, I'll either wait for them to get this patch or make a custom GNU MCU Eclipse GCC release. I'll confirm that the bug was fixed as soon as I'll be able to build my release; Arm may equally confirm it, if they proceed with their release sooner. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/24065] 32-bit objcopy fails with '64-bit address ... out of range ...'
https://sourceware.org/bugzilla/show_bug.cgi?id=24065 --- Comment #3 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Tamar Christina : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e3ecd631339aaa2a4af57f59f0694671d4ce00ab commit e3ecd631339aaa2a4af57f59f0694671d4ce00ab Author: Tamar Christina Date: Tue Jan 8 14:52:53 2019 + Add testcase for PR/24065. This adds a new testcase for objcopy -O ihex to test that it correctly works. binutils/ChangeLog: PR 24065 * testsuite/binutils-all/copy-6.d: New test. * testsuite/binutils-all/objcopy.exp: Use it. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/24065] 32-bit objcopy fails with '64-bit address ... out of range ...'
https://sourceware.org/bugzilla/show_bug.cgi?id=24065 Tamar Christina changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Tamar Christina --- fixed in master. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/22831] ld causes massive thrashing if object files are not fully memory-resident: new algorithm needed
https://sourceware.org/bugzilla/show_bug.cgi?id=22831 --- Comment #22 from Luke Kenneth Casson Leighton --- Created attachment 11522 --> https://sourceware.org/bugzilla/attachment.cgi?id=11522=edit repro test case attached is a test file that can generate a Makefile and associated header and c files that will easily exceed the capacity of a 64-bit system to cope with. here are arguments to the script that will cause GNU ld to attempt to create an EIGHTEEN GIGABYTE executable. $ python evil_linker_torture.py 3000 400 200 50 a 32-bit system will be completely unable to cope with this, as it hopelessly exceeds the 4GB resident limit by 450%. when compiled on a 64-bit system it was necessary to terminate it with prejudice, as by the time it got to 9.5GB resident memory it was in danger of putting the compile host into severe and irrecoverable swap thrashing. if the Makefile is modified to include the option "-Wl,--no-keep-memory", the following output is generated and the errors result in the link phase terminating unsuccessfully. ld: warning: cannot find entry symbol _start; defaulting to 00401000 ld: src9.o: in function `fn_9_0': /home/lkcl/src/ld_torture/src9.c:3006:(.text+0x27): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_1149_322' defined in .text section in src1149.o ld: /home/lkcl/src/ld_torture/src9.c:3008:(.text+0x41): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_1387_379' defined in .text section in src1387.o ld: /home/lkcl/src/ld_torture/src9.c:3014:(.text+0x8f): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_1821_295' defined in .text section in src1821.o ld: /home/lkcl/src/ld_torture/src9.c:3015:(.text+0x9c): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_1082_189' defined in .text section in src1082.o ld: /home/lkcl/src/ld_torture/src9.c:3016:(.text+0xa9): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_183_330' defined in .text section in src183.o ld: /home/lkcl/src/ld_torture/src9.c:3024:(.text+0x111): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_162_394' defined in .text section in src162.o ld: /home/lkcl/src/ld_torture/src9.c:3026:(.text+0x12b): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_132_235' defined in .text section in src132.o ld: /home/lkcl/src/ld_torture/src9.c:3028:(.text+0x145): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_1528_316' defined in .text section in src1528.o ld: /home/lkcl/src/ld_torture/src9.c:3029:(.text+0x152): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_1178_357' defined in .text section in src1178.o ld: /home/lkcl/src/ld_torture/src9.c:3031:(.text+0x16c): relocation truncated to fit: R_X86_64_PLT32 against symbol `fn_1180_278' defined in .text section in src1180.o ld: /home/lkcl/src/ld_torture/src9.c:3035:(.text+0x1a0): additional relocation overflows omitted from the output ^Cmake: *** Deleting file `main' make: *** [main] Interrupt -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/22831] ld causes massive thrashing if object files are not fully memory-resident: new algorithm needed
https://sourceware.org/bugzilla/show_bug.cgi?id=22831 Luke Kenneth Casson Leighton changed: What|Removed |Added Priority|P2 |P1 Severity|normal |critical -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/22831] ld causes massive thrashing if object files are not fully memory-resident: new algorithm needed
https://sourceware.org/bugzilla/show_bug.cgi?id=22831 --- Comment #21 from Luke Kenneth Casson Leighton --- to emphasise that this is strategically becoming an absolutely critical bug: https://lists.debian.org/debian-devel/2019/01/msg00081.html here it has been reported that even when using -Wl,--no-keep-memory, firefox completely fails to build on a 32-bit system. the debian developers are presently testing cross-compiling 32-bit packages from 64-bit hosts. they report that ubuntu has *already* moved over to this procedure. 32 bit distributions are no longer self-hosting. this bug is now a priority 1 critical bug. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/23699] ihex output fails for mipsel-elf-objcopy
https://sourceware.org/bugzilla/show_bug.cgi?id=23699 --- Comment #13 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a9859e01726d085db79cff88550fdb38e2434e42 commit a9859e01726d085db79cff88550fdb38e2434e42 Author: Alan Modra Date: Tue Jan 8 22:21:57 2019 +1030 PR24065, 32-bit objcopy fails with 64-bit address ... out of range PR 23699 PR 24065 * ihex.c (ihex_write_object_contents): Properly check 32-bit address range. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/24065] 32-bit objcopy fails with '64-bit address ... out of range ...'
https://sourceware.org/bugzilla/show_bug.cgi?id=24065 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a9859e01726d085db79cff88550fdb38e2434e42 commit a9859e01726d085db79cff88550fdb38e2434e42 Author: Alan Modra Date: Tue Jan 8 22:21:57 2019 +1030 PR24065, 32-bit objcopy fails with 64-bit address ... out of range PR 23699 PR 24065 * ihex.c (ihex_write_object_contents): Properly check 32-bit address range. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug ld/22831] ld causes massive thrashing if object files are not fully memory-resident: new algorithm needed
https://sourceware.org/bugzilla/show_bug.cgi?id=22831 --- Comment #20 from Luke Kenneth Casson Leighton --- ok so i spoke to dr stallman a couple of weeks ago, and he confirmed that code that is near-identical to that which i described in the very first comment of this bugreport was REMOVED some time in the late 1990s, by persons not familiar with the type of issues that linking has to deal with. the original code that dr stallman wrote did two things: (1) checked to make absolutely sure that it stayed within the bounds of RESIDENT available memory, if it could. (2) that it ONLY loaded into memory the maximum number of object files that would ensure that it remained within bounds of resident available memory, if it could. this code is essential to research and restore its functionality. this is NOT a 32-bit-only problem. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/24044] FTB with GCC libiberty: binutils/stabs.c:3042: undefined reference to `cplus_mangle_opname'
https://sourceware.org/bugzilla/show_bug.cgi?id=24044 --- Comment #6 from Nick Clifton --- Hi Alan, > (and thus c++filt has strip_underscore set by default). The new tests need > --no-strip-underscores. Doh! That was what I was missing. Thanks for pointing this out. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
