diff options
| author | Tom Tromey <tromey@adacore.com> | 2024-03-28 13:22:34 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2024-04-02 08:57:24 -0600 |
| commit | 1e459e6625ff86babc461f8ceada0a63aee5b7a5 (patch) | |
| tree | 239a45bf58417cfd7aa7d98dbddab66ee170237a /libgcc | |
| parent | a7aa9455a8b9cb080649a7357b7360f2d99bcbf1 (diff) | |
| download | gcc-1e459e6625ff86babc461f8ceada0a63aee5b7a5.zip gcc-1e459e6625ff86babc461f8ceada0a63aee5b7a5.tar.gz gcc-1e459e6625ff86babc461f8ceada0a63aee5b7a5.tar.bz2 | |
Prettify output of debug_dwarf_die
When debugging gcc, I tried calling debug_dwarf_die and I saw this
output:
DW_AT_location: location descriptor:
(0x7fffe9c2e870) DW_OP_dup 0, 0
(0x7fffe9c2e8c0) DW_OP_bra location descriptor (0x7fffe9c2e640)
, 0
(0x7fffe9c2e820) DW_OP_lit4 4, 0
(0x7fffe9c2e910) DW_OP_skip location descriptor (0x7fffe9c2e9b0)
, 0
(0x7fffe9c2e640) DW_OP_dup 0, 0
I think those ", 0" should not appear on their own lines. The issue
seems to be that print_dw_val should not generally emit a newline,
except when recursing.
gcc/ChangeLog
* dwarf2out.cc (print_dw_val) <dw_val_class_loc>: Don't
print newline when not recursing.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions