[Bug debug/115943] g++ generates contradictory line table entries

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115943 --- Comment #9 from Guinevere Larsen --- (In reply to Andrew Pinski from comment #8) > (In reply to Guinevere Larsen from comment #7) > > I understand that you could have multiple lines related to a single > > instruction (even if I disagree it

[Bug debug/115945] DW_LNE_set_discriminator emitted right before Special Opcodes

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115945 --- Comment #6 from Guinevere Larsen --- I don't have experience reading debug information in this format, and I don't know how to turn this to a format I know (gdb, readelf or objdump). However, I think the important section would be this:

[Bug debug/115945] DW_LNE_set_discriminator emitted right before Special Opcodes

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115945 --- Comment #4 from Guinevere Larsen --- Sorry, I should have been more clear. This happens for the last entry of line 11, after returning from `p.get()->call()`. > Is this a bug in binutils due to the .loc output or should the .loc output be

[Bug debug/115943] g++ generates contradictory line table entries

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115943 --- Comment #7 from Guinevere Larsen --- I understand that you could have multiple lines related to a single instruction (even if I disagree it should happen at -Og). My question is, why is it ok for an entry to have is_stmt and !is_stmt for the

[Bug debug/115945] New: DW_LNE_set_discriminator emitted right before Special Opcodes

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115945 Bug ID: 115945 Summary: DW_LNE_set_discriminator emitted right before Special Opcodes Product: gcc Version: 14.1.1 Status: UNCONFIRMED Severity: normal

[Bug c++/115944] Incorrect code generation with -Og

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115944 Guinevere Larsen changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/115944] Incorrect code generation with -Og

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115944 Guinevere Larsen changed: What|Removed |Added Component|debug |c++ --- Comment #1 from Guinevere La

[Bug debug/115943] g++ generates contradictory line table entries

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115943 --- Comment #4 from Guinevere Larsen --- Could you explain why having a single instruction be a statement and not a statement at once is expected? Or is that why you marked this bug as a duplicate of 95574?

[Bug debug/115944] New: Incorrect code generation with -Og

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115944 Bug ID: 115944 Summary: Incorrect code generation with -Og Product: gcc Version: 14.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug

[Bug debug/115943] New: g++ generates contradictory line table entries

2024-07-15 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115943 Bug ID: 115943 Summary: g++ generates contradictory line table entries Product: gcc Version: 14.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c++/105024] New: g++ generates wrong line debug information

2022-03-22 Thread blarsen at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105024 Bug ID: 105024 Summary: g++ generates wrong line debug information Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++