public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/99588] variable set but not used warning on static _Atomic assignment Date: Tue, 16 Mar 2021 20:28:59 +0000 [thread overview] Message-ID: <bug-99588-4-WxZ6w4i19d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99588-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99588 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |89180 CC| |egallager at gcc dot gnu.org, | |eggert at gnu dot org --- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> --- I think there's another similar bug against GCC out there that this one is reminding me of, but I can't seem to remember the number or find it right now though... I think Paul Eggert either reported or was on cc for it, though, so maybe he knows? (or maybe I'm just imagining things in which case I'm sorry) Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89180 [Bug 89180] [meta-bug] bogus/missing -Wunused warnings
next prev parent reply other threads:[~2021-03-16 20:28 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-15 1:53 [Bug c/99588] New: " godmar at gmail dot com 2021-03-15 8:55 ` [Bug c/99588] " rguenth at gcc dot gnu.org 2021-03-16 20:28 ` egallager at gcc dot gnu.org [this message] 2021-03-18 11:29 ` jakub at gcc dot gnu.org 2021-03-18 13:14 ` jakub at gcc dot gnu.org 2021-03-19 21:55 ` cvs-commit at gcc dot gnu.org 2021-03-19 21:56 ` jakub at gcc dot gnu.org 2021-03-30 22:41 ` cvs-commit at gcc dot gnu.org 2021-03-31 6:46 ` jakub at gcc dot gnu.org 2021-04-20 23:33 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:51 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:11 ` jakub at gcc dot gnu.org 2021-09-11 14:24 ` pinskia 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-99588-4-WxZ6w4i19d@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).