public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/111409] Invalid .debug_macro.dwo macro information for split DWARF Date: Wed, 20 Sep 2023 06:03:26 +0000 [thread overview] Message-ID: <bug-111409-4-t010lNYdlN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111409 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:80048aa13a6b55d2be485000840a4e1c8b57d8e7 commit r14-4165-g80048aa13a6b55d2be485000840a4e1c8b57d8e7 Author: Omar Sandoval <osandov@osandov.com> Date: Wed Sep 13 23:41:22 2023 -0700 debug/111409 - don't generate COMDAT macro sections for split DWARF Split DWARF files aren't processed by the linker, so DW_MACRO_import offsets aren't relocated and the .debug_macro.dwo sections aren't deduplicated and merged. There's no clear way for this to work for split DWARF, so disable it. gcc/ChangeLog: PR debug/111409 * dwarf2out.cc (output_macinfo): Don't call optimize_macinfo_range if dwarf_split_debug_info. gcc/testsuite/ChangeLog: PR debug/111409 * gcc.dg/pr111409.c: New test.
next prev parent reply other threads:[~2023-09-20 6:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-13 21:29 [Bug debug/111409] New: " osandov at osandov dot com 2023-09-14 6:51 ` [Bug debug/111409] " osandov at osandov dot com 2023-09-20 6:03 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-28 12:58 ` ro at gcc dot gnu.org 2024-02-27 0:57 ` osandov at osandov dot com 2024-05-21 15:04 ` vries at gcc dot gnu.org 2024-05-21 15:05 ` vries 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-111409-4-t010lNYdlN@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).