public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59950] [9/10/11/12 Regression] Bogus diagnostic "taking address of temporary" taking address of trivial no-op assignment to temporary with empty class
Date: Thu, 02 Dec 2021 04:47:51 +0000 [thread overview]
Message-ID: <bug-59950-4-Bn319rkp8g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59950-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59950
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #2)
> The current top of 6.0 trunk still issues the bogus diagnostic. Confirming
> also with prior versions.
Note this example is different as it worked in 4.6.4 but the first example
failed in 4.6.4.
next prev parent reply other threads:[~2021-12-02 4:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 19:40 [Bug c++/59950] New: Bogus diagnostic "taking address of temporary" taking address of trivial no-op assignment to temporary richard-gccbugzilla at metafoo dot co.uk
2014-01-26 21:52 ` [Bug c++/59950] " richard-gccbugzilla at metafoo dot co.uk
2015-03-19 10:05 ` paolo.carlini at oracle dot com
2021-12-02 4:47 ` pinskia at gcc dot gnu.org [this message]
2021-12-02 4:59 ` [Bug c++/59950] [9/10/11/12 Regression] Bogus diagnostic "taking address of temporary" taking address of trivial no-op assignment to temporary with empty class pinskia at gcc dot gnu.org
2021-12-02 5:04 ` pinskia at gcc dot gnu.org
2022-01-24 4:45 ` jason at gcc dot gnu.org
2022-01-25 19:28 ` cvs-commit at gcc dot gnu.org
2022-01-25 19:32 ` [Bug c++/59950] [9/10/11 " jason at gcc dot gnu.org
2022-03-18 13:32 ` ppalka at gcc dot gnu.org
2022-03-22 5:18 ` cvs-commit at gcc dot gnu.org
2022-03-26 23:27 ` [Bug c++/59950] [9/10 " jason at gcc dot gnu.org
2022-05-12 21:15 ` cvs-commit at gcc dot gnu.org
2022-05-13 17:41 ` [Bug c++/59950] [9 " cvs-commit at gcc dot gnu.org
2022-05-13 17:49 ` jason at gcc dot gnu.org
2022-07-31 8:50 ` redi 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-59950-4-Bn319rkp8g@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).