[Bug ld/31466] It takes a long time to build Rust program with --no-keep-memory

2024-03-08 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 --- Comment #9 from Alan Modra --- Perhaps it would be better to just drop the mmap change in _bfd_elf_link_keep_memory. I did wonder when reviewing that patch whether it was a good idea to discard things just based on whether mmap was

[Bug ld/31466] It takes a long time to build Rust program with --no-keep-memory

2024-03-08 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 --- Comment #8 from H.J. Lu --- Created attachment 15395 --> https://sourceware.org/bugzilla/attachment.cgi?id=15395=edit This patch is on top of the mmap patches -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/31466] It takes a long time to build Rust program with --no-keep-memory

2024-03-08 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 --- Comment #7 from Sam James --- That's looking good, thanks! I'll run it overnight on top of mmap (needed trivial rebasing) with the package builds. If needed, I can do a separate large build with -Wl,--no-keep-memory and just this patch

[Bug ld/31466] It takes a long time to build Rust program with --no-keep-memory

2024-03-08 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 --- Comment #6 from H.J. Lu --- Created attachment 15394 --> https://sourceware.org/bugzilla/attachment.cgi?id=15394=edit Try this -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/31466] It takes a long time to build Rust program with --no-keep-memory

2024-03-08 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 H.J. Lu changed: What|Removed |Added Summary|Hang when building Rust |It takes a long time to

[Bug ld/31466] Hang when building Rust program with --no-keep-memory

2024-03-08 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 H.J. Lu changed: What|Removed |Added CC||amodra at gmail dot com -- You are

[Bug ld/31466] Hang when building Rust program with --no-keep-memory

2024-03-08 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 H.J. Lu changed: What|Removed |Added Version|unspecified |2.43 (HEAD) Assignee|unassigned

[Bug ld/31466] Hang when building Rust program with mmap patches

2024-03-08 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 --- Comment #3 from Sam James --- As the backtrace hinted, if I drop -Wl,--gc-sections, it completes quickly. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/31327] libbacktrace test failures

2024-03-08 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=31327 --- Comment #5 from Sam James --- Thank you both. Done at https://inbox.sourceware.org/gdb/87plw4r5ta@gentoo.org/T/#u. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/31466] Hang when building Rust program with mmap patches

2024-03-08 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 --- Comment #2 from Sam James --- With binutils-2.42, it takes about 1-2s. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/31466] Hang when building Rust program with mmap patches

2024-03-08 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 --- Comment #1 from Sam James --- Tarball is at https://dev.gentoo.org/~sam/bugs/sourceware/31466/ld-hang-PR31466.tar.xz. Inside, run: ``` gcc -m64 symbols.o procs-bf23c8fa176eac21.procs.d1865a8196e0707d-cgu.0.rcgu.o -Wl,--as-needed -L deps

[Bug ld/31466] New: Hang when building Rust program with mmap patches

2024-03-08 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=31466 Bug ID: 31466 Summary: Hang when building Rust program with mmap patches Product: binutils Version: unspecified Status: NEW Severity: normal Priority: P2

[Bug gas/31464] GCC 6.4 failed to build binutils

2024-03-08 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31464 H.J. Lu changed: What|Removed |Added Status|NEW |RESOLVED Target Milestone|---

[Bug gas/31464] GCC 6.4 failed to build binutils

2024-03-08 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=31464 --- Comment #1 from Sourceware Commits --- The master branch has been updated by H.J. Lu : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=03fa0c63d3a5944afcf031ecf0b433b2985e6eeb commit 03fa0c63d3a5944afcf031ecf0b433b2985e6eeb

[Bug gas/31464] New: GCC 6.4 failed to build binutils

2024-03-08 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31464 Bug ID: 31464 Summary: GCC 6.4 failed to build binutils Product: binutils Version: 2.43 (HEAD) Status: NEW Severity: normal Priority: P2 Component: gas

[Bug binutils/31327] libbacktrace test failures

2024-03-08 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31327 --- Comment #4 from Nick Clifton --- (In reply to Sam James from comment #2) > OK, I get what's happening here. > > This ended up being > https://github.com/ianlancetaylor/libbacktrace/issues/118 which is fixed > upstream. > > Nick, or

[Bug binutils/29505] xxx-w64-mingw32-objdump takes a long time to scan pe binaries for debug information

2024-03-08 Thread ralf.habacker at freenet dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=29505 --- Comment #17 from Ralf Habacker --- (In reply to Nick Clifton from comment #14) > I am guessing that such an option would not make a lot of difference, > since the debug information will still have to be loaded and scanned. > > But that

[Bug ld/31461] score-elf buffer overflow

2024-03-08 Thread sam at gentoo dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=31461 Sam James changed: What|Removed |Added CC||sam at gentoo dot org -- You are