[Bug ld/30343] LTO ignores linker reference to _pei386_runtime_relocator

2023-04-18 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30343 Alan Modra changed: What|Removed |Added Assignee|amodra at gmail dot com|unassigned at sourceware dot org

[Bug ld/30343] LTO drops explicitly referenced symbol _pei386_runtime_relocator

2023-04-18 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30343 --- Comment #1 from Alan Modra --- Created attachment 14841 --> https://sourceware.org/bugzilla/attachment.cgi?id=14841&action=edit run pe after_open earlier This cures the _pei386_runtime_relocator problem but unfortunately results in "und

[Bug ld/30343] LTO drops explicitly referenced symbol _pei386_runtime_relocator

2023-04-18 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30343 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[Bug gprofng/30360] [gprofng collect] Seg. Fault when application uses std::thread

2023-04-18 Thread vladimir.mezentsev at oracle dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30360 Vladimir Mezentsev changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNE

[Bug ld/30359] Create Resource-Only DLL

2023-04-18 Thread pali at kernel dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 --- Comment #2 from Pali Rohár --- If adding empty import table and something in code .text sections is feature of the linker, it is somewhere documented? What it is doing and what is putting there (as those sections are not in any user suppli

[Bug ld/30367] Performance regression after updating to 2.40

2023-04-18 Thread streetster at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30367 --- Comment #3 from Mark Street --- Just tested your proposed patch against the N64 project: root@5e98d9b5788e:/sssv# time mips-elf-ld -T sssv.ld -T undefined_syms.us.txt -T undefined_syms_auto.txt -Map build/sssv.us.map --no-check-sections -

[Bug ld/28910] GNU-ld: ARM: Issues when trying to set target output architecture

2023-04-18 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28910 --- Comment #8 from Nick Clifton --- (In reply to Stas Sergeev from comment #7) Hi Stas, > In a mean time, if your patch doesn't fix that, > then will you provide another patch? I will try to provide another patch - or an updated version of

[Bug ld/30367] Performance regression after updating to 2.40

2023-04-18 Thread matz at suse dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=30367 --- Comment #2 from Michael Matz --- No need to dig into trying with an empty ROM. It's easily reproducable with many input files each being used in a wildstatement of a linker script. It's a quadraticness problem. Proposed fix at https:

[Bug ld/30367] Performance regression after updating to 2.40

2023-04-18 Thread matz at suse dot de
https://sourceware.org/bugzilla/show_bug.cgi?id=30367 Michael Matz changed: What|Removed |Added Last reconfirmed||2023-04-18 Ever confirmed|0

[Bug ld/28910] GNU-ld: ARM: Issues when trying to set target output architecture

2023-04-18 Thread stsp at users dot sourceforge.net
https://sourceware.org/bugzilla/show_bug.cgi?id=28910 --- Comment #7 from Stas Sergeev --- (In reply to Nick Clifton from comment #6) > It doesn't. :-( But you can fix the problem by rearranging the order of the > object files on the link command line: Thanks, waiting for the test results from

[Bug ld/28910] GNU-ld: ARM: Issues when trying to set target output architecture

2023-04-18 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=28910 --- Comment #6 from Nick Clifton --- (In reply to Stas Sergeev from comment #5) > Created attachment 14836 [details] > test case > > This test-case ends with > > ld: error: source object obj2.o has EABI version 5, but target out.o has > EABI

[Bug binutils/30355] [DWARFv5] readelf: loc_offset XX too big

2023-04-18 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30355 --- Comment #3 from Nick Clifton --- (In reply to Nick Desaulniers from comment #2) > What's the best way to strip out the debug info? > > $ objcopy --only-keep-debug vmlinux vmlinux-debug > $ du -h vmlinux vmlinux-debug > 34M vmlinux > 33

[Bug ld/30359] Create Resource-Only DLL

2023-04-18 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30359 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1