public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/105088] Small DWARF 5 spec violation in line table when passing an absolute path Date: Tue, 29 Mar 2022 08:57:29 +0000 [thread overview] Message-ID: <bug-105088-4-Z1cDUV876R@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105088-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105088 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- See the "Note that if a .debug_line_str section is present, both the compilation unit debugging information entry and the line number header can share a single copy of the current directory name string." and "Note that if a .debug_line_str section is present, both the compilation unit debugging information entry and the line number header can share a single copy of the current file name string." comments. The reason for the duplication (DW_AT_comp_dir of CU vs. dir 0 entry in .debug_line and DW_AT_name of CU vs. file 0 entry in .debug_line) is so that .debug_info can be stripped and .debug_line* kept.
next prev parent reply other threads:[~2022-03-29 8:57 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-28 17:38 [Bug debug/105088] New: " simon.marchi at polymtl dot ca 2022-03-28 17:48 ` [Bug debug/105088] " simon.marchi at polymtl dot ca 2022-03-29 7:37 ` rguenth at gcc dot gnu.org 2022-03-29 8:33 ` marxin at gcc dot gnu.org 2022-03-29 8:35 ` jakub at gcc dot gnu.org 2022-03-29 8:39 ` jakub at gcc dot gnu.org 2022-03-29 8:48 ` ebotcazou at gcc dot gnu.org 2022-03-29 8:52 ` jakub at gcc dot gnu.org 2022-03-29 8:57 ` jakub at gcc dot gnu.org [this message] 2022-03-29 9:19 ` ebotcazou at gcc dot gnu.org 2022-03-29 9:24 ` jakub at gcc dot gnu.org 2022-03-29 12:24 ` mark 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-105088-4-Z1cDUV876R@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).