public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/107536] [12/13/14 regression] Wrong 'not referenced' warning on renamed variable Date: Thu, 11 May 2023 15:49:23 +0000 [thread overview] Message-ID: <bug-107536-4-bCNqeUhfYU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107536-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107536 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot gnu.org Status|UNCONFIRMED |NEW Last reconfirmed| |2023-05-11 Ever confirmed|0 |1 --- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- The variable is macro-substituted and indeed fools the warning.
prev parent reply other threads:[~2023-05-11 15:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-05 17:00 [Bug ada/107536] New: [12 " simon at pushface dot org 2022-11-07 7:01 ` [Bug ada/107536] [12/13 " rguenth at gcc dot gnu.org 2022-11-08 11:29 ` simon at pushface dot org 2023-05-08 12:25 ` [Bug ada/107536] [12/13/14 " rguenth at gcc dot gnu.org 2023-05-11 15:49 ` ebotcazou at gcc dot gnu.org [this message]
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-107536-4-bCNqeUhfYU@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).