public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/99319] New: DW_MACRO_define_strp uses uleb128 for second operand Date: Mon, 01 Mar 2021 14:50:55 +0000 [thread overview] Message-ID: <bug-99319-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99319 Bug ID: 99319 Summary: DW_MACRO_define_strp uses uleb128 for second operand Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org Target Milestone: --- Consider compiling hello world, with macro info: ... $ gcc-11 -ggdb3 -g hello.c -dA -save-temps ... In a-hello.s, we have: ... .section .debug_macro,"",@progbits .Ldebug_macro0: .value 0x5 # DWARF macro version number .byte 0x2 # Flags: 32-bit, lineptr present .long .Ldebug_line0 .byte 0x3 # Start new file .uleb128 0 # Included from line number 0 .uleb128 0x1 # file hello.c .byte 0x5 # Define macro strp .uleb128 0 # At line number 0 .long .LASF2 # The macro: "__STDC__ 1" ... So, the DW_MACRO_define_strp entry (starting with .byte 0x5) has two operands, a uleb128 and a .long. AFAIU, this is in accordance with the spec: ... A DW_MACRO_define_strp or DW_MACRO_undef_strp entry has two operands. The first operand encodes the source line number of the #define or #undef macro directive. The second operand consists of an offset into a string table contained in the .debug_str section of the object file. The size of the operand is given in the header offset_size_flag field. ... Now add -gsplit-dwarf: ... $ gcc-11 -ggdb3 -g hello.c -dA -save-temps -gsplit-dwarf ... Now we have instead: ... .section .debug_macro.dwo,"e",@progbits .Ldebug_macro0: .value 0x5 # DWARF macro version number .byte 0x2 # Flags: 32-bit, lineptr present .long .Lskeleton_debug_line0 .byte 0x3 # Start new file .uleb128 0 # Included from line number 0 .uleb128 0x1 # file hello.c .byte 0x5 # Define macro strp .uleb128 0 # At line number 0 .uleb128 0x191 # The macro: "__STDC__ 1" ... The second operand is now also a .uleb128. AFAIU, this goes against the spec.
next reply other threads:[~2021-03-01 14:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-01 14:50 vries at gcc dot gnu.org [this message] 2021-03-01 14:51 ` [Bug debug/99319] " vries at gcc dot gnu.org 2021-03-01 15:18 ` vries at gcc dot gnu.org 2021-03-01 15:30 ` jakub at gcc dot gnu.org 2021-03-02 17:26 ` cvs-commit at gcc dot gnu.org 2021-03-02 17:32 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-99319-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).