[Bug debug/82011] [8 regression] early lto debug causes dsymutil warning on Darwin

2017-08-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82011 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug debug/82011] [8 regression] early lto debug causes dsymutil warning on Darwin

2017-08-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82011 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug debug/82011] [8 regression] early lto debug causes dsymutil warning on Darwin

2017-08-29 Thread ro at CeBiTec dot Uni-Bielefeld.DE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82011 --- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #1 from Richard Biener --- > Ok, so a simple checking patch like the following unfortunately fires > right and left, restricting it to DW_AT_inline doesn't fire for me on

[Bug debug/82011] [8 regression] early lto debug causes dsymutil warning on Darwin

2017-08-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82011 --- Comment #2 from Richard Biener --- Ok. I think I left some dead (but not so dead as it appears) code in gen_subprogram_die. So I am testing (together with the verification) Index: gcc/dwarf2out.c

[Bug debug/82011] [8 regression] early lto debug causes dsymutil warning on Darwin

2017-08-29 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82011 --- Comment #1 from Richard Biener --- Ok, so a simple checking patch like the following unfortunately fires right and left, restricting it to DW_AT_inline doesn't fire for me on the testcase you mention (add || a->dw_attr != DW_AT_inline to the

[Bug debug/82011] [8 regression] early lto debug causes dsymutil warning on Darwin

2017-08-28 Thread ro at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82011 Rainer Orth changed: What|Removed |Added Target Milestone|--- |8.0