[Bug gas/27193] Linkonce section with unused section symbols won't match comdat section without unused section symbols

2021-01-18 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=27193 --- Comment #13 from Matt Godbolt --- Thank you all so much! -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gas/27193] GCC trunk unable to bootstrap with Binutils Trunk

2021-01-16 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=27193 --- Comment #7 from Matt Godbolt --- Hi there, It was failing until pretty recently. Our fix is to go back to 2.35.1 (which is more sane). Seems like you've been able to repro: please let me know if I can test anything! Cheers all, Matt --

[Bug gas/27193] GCC trunk unable to bootstrap with Binutils Trunk

2021-01-16 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=27193 Matt Godbolt changed: What|Removed |Added CC||matt at godbolt dot org -- You are

[Bug binutils/25876] Demangling support for "spaceship operator"

2020-04-27 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=25876 --- Comment #2 from Matt Godbolt --- Thanks for your patience and help here! I never quite know where the boundaries lie! Much appreciated, Matt -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/25876] New: Demangling support for "spaceship operator"

2020-04-25 Thread matt at godbolt dot org
iority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: matt at godbolt dot org Target Milestone: --- c++filt does not support the new C++ `operator <=>`, instead showing mangled names like "_ZNK3FoossERKS_". (Example at https://githu

[Bug gold/13442] gold screws up exception handling with --incremental flag

2017-01-11 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=13442 Matt Godbolt changed: What|Removed |Added CC||matt at godbolt dot org --- Comment

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-30 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #36 from Matt Godbolt --- Ok; with a GCC 6 snapshot build (20160221) there's no crash when I link with -fdump-ipa-all I will tar up the results and send you an email with the link. -- You are receiving this mail because: You are

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-30 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #35 from Matt Godbolt --- Hi Honza, I checkout the branch of my code where the problem exists and confirmed I could reproduce. Then I re-linked with =-save-temps -fdump-ipa-all and sadly I get an ICE: GNU GIMPLE (DRW-internal-bui

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-30 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #33 from Matt Godbolt --- Yes, I can do that. I'll get back to you with the relevant information as soon as I can. On Wed, Mar 30, 2016 at 10:23 AM hubicka at ucw dot cz < sourceware-bugzi...@sourceware.org> wrote: > https://sour

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-30 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #31 from Matt Godbolt --- Hi all, Just following up on this as it seems to have stalled: @honza, do you concur this may be a bug in GCC? If so shall I file something, or are you happy to capture it appropriately? Thanks, Matt --

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-21 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #14 from Matt Godbolt --- I've sent my full results to H.J.Lu and Cary directly. Thanks both. -- You are receiving this mail because: You are on the CC list for the bug. ___ bug-binutil

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-21 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #13 from Matt Godbolt --- Thanks, I will do. grepping the -v output: $ grep '_ZNSt8functionIFvvEED[12]Ev' gcc_verbose_output /tmp/gcc/bin/../lib/gcc/x86_64-linux-gnu/5.2.0/../../../../x86_64-linux-gnu/bin/ld: out/haswell/main/Sy

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-21 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #11 from Matt Godbolt --- Hi H.J. Lu, I've made a build of your binutils, supplied -Wl,-plugin-save-temps and kept all the files generated. I will share the files with you over email. Looking at the ltrans1.o file generated with

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-21 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #9 from Matt Godbolt --- Hi H.J.Hu, Cary already made a patched binutils (users/ccoutant/gold-record) which does a similar thing: that's how Cary was able to debug further. Would it be useful for me to build your branch too and g

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-20 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #6 from Matt Godbolt --- I just tried with a snapshot build of GCC I had around (6.0.0 20160221), and the problem persists: Dump of assembler code for function std::_List_node >::~_List_node(): 0x0077434c <+0>: push

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-20 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #5 from Matt Godbolt --- Wow! What an awesome diagnosis: thank you so much for digging in to this! I've tried with GCC 5.3.0 but not any GCC 6+ snapshots. The GCC guys on the mailing list didn't seem to think it was a GCC bug init

[Bug gold/19842] LTO build fails to write call address for weak symbol reference

2016-03-19 Thread matt at godbolt dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=19842 --- Comment #3 from Matt Godbolt --- Hi Cary, The output of even the compiled files is somewhat sensitive. Would it be possible to email them directly to you instead of placing them here? Also; the process you described left some .o files as

[Bug gold/19842] New: LTO build fails to write call address for weak symbol reference

2016-03-18 Thread matt at godbolt dot org
Priority: P2 Component: gold Assignee: ccoutant at gmail dot com Reporter: matt at godbolt dot org CC: ian at airs dot com Target Milestone: --- I have a large, proprietary project which links with an open source project. The large project ("