public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sagebar at web dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/111080] [11/12/13/14 Regression] restrict qualifier causes extra debug info to happen Date: Sun, 20 Aug 2023 09:34:27 +0000 [thread overview] Message-ID: <bug-111080-4-g9i2nRpteJ@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 #2 from sagebar at web dot de --- @Andrew Pinski Of course: yes. I did make a mistake there, but only for this case: > int (*fun_t)(struct foo *); // Leak (even w/o restrict!) asm: ... .globl fun_t .section .bss .align 4 .type fun_t, @object .size fun_t, 4 fun_t: .zero 4 ... In the other case: > static int (*fun_t)(struct foo *); // Leak (even w/o restrict!) asm: ... # No data-symbol is generated for `fun_t` ... Gcc actually doesn't generate a .bss-symbol for the static variable (since it's unused), but it still generates debug inforation for `struct foo`. So I guess strike `int (*fun_t)(struct foo *);` from the list, but keep `static int (*fun_t)(struct foo *);` which still leaks
next prev parent reply other threads:[~2023-08-20 9:34 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 [this message] 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 ` [Bug debug/111080] [11 " cvs-commit at gcc dot gnu.org 2024-06-21 9:38 ` 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-g9i2nRpteJ@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).