public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104142] Spurios warning unused-variable
Date: Thu, 20 Jan 2022 08:48:21 +0000 [thread overview]
Message-ID: <bug-104142-4-lOz4gvWVow@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104142-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104142
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/10/11/12] Spurios |Spurios warning
|warning unused-variable |unused-variable
Keywords| |diagnostic
Last reconfirmed| |2022-01-20
Status|UNCONFIRMED |NEW
Known to fail| |10.3.0, 11.2.0, 12.0, 9.4.0
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
'b' is likely not marked readonly as it is initialized.
next prev parent reply other threads:[~2022-01-20 8:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 8:42 [Bug c++/104142] New: [9/10/11/12] " phdiv at fastmail dot fm
2022-01-20 8:48 ` rguenth at gcc dot gnu.org [this message]
2022-01-21 8:32 ` [Bug c++/104142] [9/10/11/12 Regression] Spurios warning unused-variable on const static variable and defaulted constructor pinskia at gcc dot gnu.org
2022-01-28 11:32 ` jakub at gcc dot gnu.org
2022-01-28 11:43 ` jakub at gcc dot gnu.org
2022-04-11 18:52 ` jason at gcc dot gnu.org
2022-04-12 3:58 ` cvs-commit at gcc dot gnu.org
2022-05-04 2:36 ` [Bug c++/104142] [9/10/11 Regression] Spurious " mh+gcc at glandium dot org
2022-05-04 3:26 ` mh+gcc at glandium dot org
2022-05-12 20:13 ` cvs-commit at gcc dot gnu.org
2022-05-12 21:25 ` [Bug c++/104142] [9/10 " cvs-commit at gcc dot gnu.org
2022-05-27 9:47 ` [Bug c++/104142] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-07-07 9:55 ` 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-104142-4-lOz4gvWVow@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: link
Be 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).