[Bug gold/26200] ld terminated with signal 11 with LTO and -Wl,--thread-count=2
https://sourceware.org/bugzilla/show_bug.cgi?id=26200 Martin Liska changed: What|Removed |Added CC||nick.gasson at arm dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/26200] ld terminated with signal 11 with LTO and -Wl,--thread-count=2
https://sourceware.org/bugzilla/show_bug.cgi?id=26200 --- Comment #7 from Nick Gasson --- (In reply to H.J. Lu from comment #4) > This helps. But it doesn't fix the problem. > When you say it doesn't fix the problem, perhaps you were running into the --threads segfault in bug 26827? I tried latest master with your patch above and the attached test case doesn't crash any more. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/26200] ld terminated with signal 11 with LTO and -Wl,--thread-count=2
https://sourceware.org/bugzilla/show_bug.cgi?id=26200 --- Comment #8 from Martin Liska --- (In reply to Nick Gasson from comment #7) > (In reply to H.J. Lu from comment #4) > > This helps. But it doesn't fix the problem. > > > > When you say it doesn't fix the problem, perhaps you were running into the > --threads segfault in bug 26827? I tried latest master with your patch above > and the attached test case doesn't crash any more. It's a different problem related to a LTO plug-in. Please see H.J. brief analysis. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/23847] New warning on i586: -Werror=absolute-value
https://sourceware.org/bugzilla/show_bug.cgi?id=23847 Martin Liska changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Martin Liska --- This one is resolved by 453f8e1e491. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/26381] gas: speed of LTO LTRANS units
https://sourceware.org/bugzilla/show_bug.cgi?id=26381 Martin Liska changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Martin Liska --- Thanks to Alan, I would consider this resolved. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/22967] nm should distinguish in between local and global ifunc
https://sourceware.org/bugzilla/show_bug.cgi?id=22967 --- Comment #6 from Martin Liska --- @Nick: May I please remind you this issue? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/22967] nm should distinguish in between local and global ifunc
https://sourceware.org/bugzilla/show_bug.cgi?id=22967 --- Comment #7 from Nick Clifton --- (In reply to Martin Liska from comment #6) > @Nick: May I please remind you this issue? Doh! Sorry - really dropped the ball on this one. Looking into it now. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/26200] ld terminated with signal 11 with LTO and -Wl,--thread-count=2
https://sourceware.org/bugzilla/show_bug.cgi?id=26200 --- Comment #9 from Nick Gasson --- (In reply to Martin Liska from comment #8) > > > > When you say it doesn't fix the problem, perhaps you were running into the > > --threads segfault in bug 26827? I tried latest master with your patch above > > and the attached test case doesn't crash any more. > > It's a different problem related to a LTO plug-in. Please see H.J. brief > analysis. I mean you need to apply both patches - the one from comment 4 and the one from bug 26827 - in order not to get a segfault. I tried your test case after applying both and it no longer crashes. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/22967] nm should distinguish in between local and global ifunc
https://sourceware.org/bugzilla/show_bug.cgi?id=22967 --- Comment #8 from Nick Clifton --- Created attachment 12942 --> https://sourceware.org/bugzilla/attachment.cgi?id=12942&action=edit Proposed patch Hi Martin, Please could you try out this patch and let me know what you think. The patch makes two changes. Firstly it adds a new configure time option --enable-f-for-ifunc-symbols, which if used makes nm display f for local ifuncs and F for global ifuncs. By default however this feature is not enabled. The second change is to add a new command line option to nm --ifunc-chars=CHARS. If used then nm with display CHARS[0] for global ifunc symbols and CHARS[1] for local ifunc symbols. (The local symbol can be left unspecified, in which case 'i' will be used). Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/26200] ld terminated with signal 11 with LTO and -Wl,--thread-count=2
https://sourceware.org/bugzilla/show_bug.cgi?id=26200 H.J. Lu changed: What|Removed |Added Target Milestone|--- |2.36 --- Comment #10 from H.J. Lu --- A patch is posted at https://sourceware.org/pipermail/binutils/2020-November/114021.html -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/26200] ld terminated with signal 11 with LTO and -Wl,--thread-count=2
https://sourceware.org/bugzilla/show_bug.cgi?id=26200 --- Comment #11 from Martin Liska --- Great, thank you both for the fix. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/26847] New: readelf -wi should print DWARF forms
https://sourceware.org/bugzilla/show_bug.cgi?id=26847 Bug ID: 26847 Summary: readelf -wi should print DWARF forms Product: binutils Version: unspecified Status: NEW Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- When examining DWARF, it is sometimes useful to see the DWARF form for attributes. It would be handy if readelf and objdump could display this. Note that eu-readelf does: [2e]variable abbrev: 2 name (strp) "ada_main__gnat_argc" The "(strp)" indicates the form. -- You are receiving this mail because: You are on the CC list for the bug.
Issue 24906 in oss-fuzz: binutils:fuzz_readelf: Abrt with empty stacktrace
Updates: Labels: Deadline-Approaching Comment #2 on issue 24906 by sheriffbot: binutils:fuzz_readelf: Abrt with empty stacktrace https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24906#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
