[Bug debug/111740] New: Incorrect DWARF expression generated at specific live range

2023-10-09 Thread king.chung at manchester dot ac.uk via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111740 Bug ID: 111740 Summary: Incorrect DWARF expression generated at specific live range Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal

[Bug debug/111716] call site parameter not matching with formal parameter

2023-10-06 Thread king.chung at manchester dot ac.uk via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111716 --- Comment #3 from King Lok Chung --- (In reply to Andrew Pinski from comment #1) > (In reply to King Lok Chung from comment #0) > > I also find that the type of the parameter is not propagated correctly. For > > example, an array type is

[Bug debug/111716] New: call site parameter not matching with formal parameter

2023-10-06 Thread king.chung at manchester dot ac.uk via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111716 Bug ID: 111716 Summary: call site parameter not matching with formal parameter Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug debug/111680] DWARF information inconsistent with the generated RISC-V Binary

2023-10-03 Thread king.chung at manchester dot ac.uk via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111680 --- Comment #8 from King Lok Chung --- It also looks like to me that the compiler is trying to be smart and save one register use by reusing the SP, resulting in two SP offsets. In reality, it could have used a6 or a7 easily. Or might be the

[Bug debug/111680] New: DWARF information inconstant with the generated RISC-V Binary

2023-10-03 Thread king.chung at manchester dot ac.uk via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111680 Bug ID: 111680 Summary: DWARF information inconstant with the generated RISC-V Binary Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal