[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-09-06 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 Richard Biener changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-08-12 Thread trass3r at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #27 from Trass3r --- (In reply to rguent...@suse.de from comment #25) > I fear this is the libbfd dwarf reader simply not coping with > DW_AT_abstract_origin in other CUs, being confused as to which > abbrev section it needs to look

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-08-12 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 Jakub Jelinek changed: What|Removed |Added Target Milestone|9.2 |9.3 --- Comment #26 from Jakub Jelinek

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-27 Thread rguenther at suse dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #25 from rguenther at suse dot de --- On Sun, 26 May 2019, hoganmeier at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 > > --- Comment #22 from krux --- > I can also reproduce it without any linker

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-26 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #24 from krux --- objdump -dCrS also prints these errors. It definitely fails to find the entry for main which is present according to objdump --dwarf: <1>: Abbrev Number: 8 (DW_TAG_subprogram) DW_AT_external: 1

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-26 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #23 from krux --- But it's so fragile, touch any part of the code and the error disappears. Like change serial3_available to void and you also get an additional symbol: 4160 0003 T mainmain.cpp:8

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-26 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #22 from krux --- I can also reproduce it without any linker script, simplified code: int serial3_available() {} struct HardwareSerial3 { int available() { serial3_available(); } }; HardwareSerial3 Serial3; void yield()

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-26 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 Iain Sandoe changed: What|Removed |Added Status|NEW |WAITING --- Comment #21 from Iain Sandoe

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-26 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #20 from krux --- Thanks your patch worked! Just fyi: llvm-dwarfdump doesn't understand call-site info: https://bugs.llvm.org/show_bug.cgi?id=41846 Not sure if it's relevant.

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-14 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #19 from Iain Sandoe --- (In reply to krux from comment #18) > (In reply to Iain Sandoe from comment #14) > > current trunk (27), manual regeneration of the > > firmware.elf.ltrans0.ltrans.o -> > > > > (it's kinda frustrating

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-14 Thread hoganmeier at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #18 from krux --- (In reply to Iain Sandoe from comment #14) > current trunk (27), manual regeneration of the > firmware.elf.ltrans0.ltrans.o -> > > (it's kinda frustrating that one can't see the link line, more tweaks are >

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #17 from Iain Sandoe --- Created attachment 46348 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46348=edit binaries for test here is the output from trunk at 27 For some reason the plugin isn't getting the "-Wl,-debug"

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #16 from Richard Biener --- (In reply to Iain Sandoe from comment #14) > (In reply to Iain Sandoe from comment #13) > > (In reply to Iain Sandoe from comment #12) > > current trunk (27), manual regeneration of the >

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #15 from Iain Sandoe --- this repeats for the compiler build from r267372, confirming some latent issue.

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #14 from Iain Sandoe --- (In reply to Iain Sandoe from comment #13) > (In reply to Iain Sandoe from comment #12) current trunk (27), manual regeneration of the firmware.elf.ltrans0.ltrans.o -> (it's kinda frustrating that one

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #13 from Iain Sandoe --- (In reply to Iain Sandoe from comment #12) > (In reply to rguent...@suse.de from comment #11) > > On Mon, 13 May 2019, iains at gcc dot gnu.org wrote: > > > > >

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #12 from Iain Sandoe --- (In reply to rguent...@suse.de from comment #11) > On Mon, 13 May 2019, iains at gcc dot gnu.org wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 > > > > --- Comment #10 from Iain Sandoe ---

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread rguenther at suse dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #11 from rguenther at suse dot de --- On Mon, 13 May 2019, iains at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 > > --- Comment #10 from Iain Sandoe --- > (In reply to Iain Sandoe from comment #9) >

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #10 from Iain Sandoe --- (In reply to Iain Sandoe from comment #9) > this is on the rev *before* the change, using llvm-dwarfdump from the llvm-7 > branch: > > iains@gcc122:~/gcc-trunk/A$ ../../llvm-710-build/bin/llvm-dwarfdump

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #9 from Iain Sandoe --- this is on the rev *before* the change, using llvm-dwarfdump from the llvm-7 branch: iains@gcc122:~/gcc-trunk/A$ ../../llvm-710-build/bin/llvm-dwarfdump --verify firmware.elf Verifying firmware.elf: file

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #8 from Richard Biener --- nm -l fw.elf also complains nm: BFD (GNU Binutils; devel:gcc / openSUSE_Leap_42.3) 2.31.1.20180828-334 assertion fail ../../bfd/dwarf2.c:3750 nm: BFD (GNU Binutils; devel:gcc / openSUSE_Leap_42.3)

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #7 from Richard Biener --- Btw, I can reproduce the nm error when linking w/o the linker script. But readelf is happy about the dwarf. I'm not sure what the llvm dwarf linter complains about with error: DIE address ranges are not

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 --- Comment #6 from Iain Sandoe --- (In reply to Richard Biener from comment #5) > Before the bisection the linker script probably managed to "fix" the debug > info > but the issue was latent. Without the linker script it works fine for me. >

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 Richard Biener changed: What|Removed |Added CC||rguenth at gcc dot gnu.org --- Comment

[Bug debug/90441] [9/10 Regression] corrupt debug info with LTO

2019-05-13 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90441 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |NEW Known to work|