public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101631] gcc permits object reference to object outside of its lifetime during constant evaluation
Date: Mon, 26 Jul 2021 20:45:10 +0000 [thread overview]
Message-ID: <bug-101631-4-TqU4qKAEt7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101631-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101631
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
Last reconfirmed| |2021-07-26
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to fsb4000 from comment #0)
> (Obligatory godbolt: https://godbolt.org/z/6qG7v9eYx)
Godbolt links are not obligatory, but a testcase is. See
https://gcc.gnu.org/bugs
next prev parent reply other threads:[~2021-07-26 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 18:46 [Bug c++/101631] New: " fsb4000 at yandex dot ru
2021-07-26 20:45 ` redi at gcc dot gnu.org [this message]
2021-07-27 2:32 ` [Bug c++/101631] " fsb4000 at yandex dot ru
2021-07-27 11:06 ` rguenth at gcc dot gnu.org
2021-07-27 14:57 ` redi at gcc dot gnu.org
2023-10-20 3:26 ` [Bug c++/101631] gcc allows for the changing of an union active member to be changed via a reference cvs-commit at gcc dot gnu.org
2023-10-25 6:04 ` sjames at gcc dot gnu.org
2023-10-26 0:19 ` nathanieloshead at gmail dot com
2023-10-26 14:58 ` ppalka at gcc dot gnu.org
2023-12-12 18:45 ` ppalka 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-101631-4-TqU4qKAEt7@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).