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/111080] [11 Regression] restrict qualifier causes extra debug info to happen Date: Fri, 21 Jun 2024 09:22:38 +0000 [thread overview] Message-ID: <bug-111080-4-4xqMJ7h4Tm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111080-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111080 --- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:80ded4e8f871c98481bab912997034b9d24b1c96 commit r11-11527-g80ded4e8f871c98481bab912997034b9d24b1c96 Author: Richard Biener <rguenther@suse.de> Date: Mon Aug 21 10:34:30 2023 +0200 debug/111080 - avoid outputting debug info for unused restrict qualified type The following applies some maintainance with respect to type qualifiers and kinds added by later DWARF standards to prune_unused_types_walk. The particular case in the bug is not handling (thus marking required) all restrict qualified type DIEs. I've found more DW_TAG_*_type that are unhandled, looked up the DWARF docs and added them as well based on common sense. PR debug/111080 * dwarf2out.c (prune_unused_types_walk): Handle DW_TAG_restrict_type, DW_TAG_shared_type, DW_TAG_atomic_type, DW_TAG_immutable_type, DW_TAG_coarray_type, DW_TAG_unspecified_type and DW_TAG_dynamic_type as to only output them when referenced. * gcc.dg/debug/dwarf2/pr111080.c: New testcase.
next prev parent reply other threads:[~2024-06-21 9:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-20 9:19 [Bug debug/111080] New: restrict qualifier leaks debug info sagebar at web dot de 2023-08-20 9:24 ` [Bug debug/111080] restrict qualifier causes extra debug info to happen pinskia at gcc dot gnu.org 2023-08-20 9:28 ` [Bug debug/111080] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-08-20 9:34 ` sagebar at web dot de 2023-08-21 8:30 ` rguenth at gcc dot gnu.org 2023-08-22 12:55 ` rguenth at gcc dot gnu.org 2023-08-24 6:23 ` cvs-commit at gcc dot gnu.org 2023-08-24 7:10 ` cvs-commit at gcc dot gnu.org 2023-08-24 7:10 ` [Bug debug/111080] [11/12 " rguenth at gcc dot gnu.org 2023-12-15 13:17 ` cvs-commit at gcc dot gnu.org 2024-06-21 9:22 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-21 9:38 ` [Bug debug/111080] [11 " rguenth 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-111080-4-4xqMJ7h4Tm@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).