[Bug debug/93988] invalid DWARF emitted for complex integer

2024-08-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93988 Andrew Pinski changed: What|Removed |Added Keywords||wrong-debug --- Comment #5 from Andrew P

[Bug debug/93988] invalid DWARF emitted for complex integer

2024-05-29 Thread vries at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93988 --- Comment #4 from Tom de Vries --- (In reply to Tom Tromey from comment #2) > Also, I see the "__unknown__" there now -- better IMO to let gdb synthesize > a name instead. Attempt to synthesize the name in gcc: ... commit d2b7f315ad976ff18c71e

[Bug debug/93988] invalid DWARF emitted for complex integer

2024-05-29 Thread vries at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93988 Tom de Vries changed: What|Removed |Added CC||vries at gcc dot gnu.org --- Comment #3 f

[Bug debug/93988] invalid DWARF emitted for complex integer

2020-03-02 Thread tromey at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93988 --- Comment #2 from Tom Tromey --- (In reply to Richard Biener from comment #1) > I wonder if there is (or should be) sth like DW_ATE_unsupported ... using > DW_ATE_lo_user is indeed unfortunate but not wrong per-se. Adding > a DW_ATE_GNU_comple

[Bug debug/93988] invalid DWARF emitted for complex integer

2020-03-02 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93988 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|