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++/772] Statement expressions issues
Date: Thu, 22 Jul 2021 21:58:05 +0000 [thread overview]
Message-ID: <bug-772-4-Ss0eZJxS7B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-772-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=772
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |89003
CC| |wilkey at drive dot ai
--- Comment #20 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 89003 has been marked as a duplicate of this bug. ***
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89003
[Bug 89003] Return inside a statement expression while initializing a static
local variable fails to cleanup cxa_guard
next prev parent reply other threads:[~2021-07-22 21:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-772-4@http.gcc.gnu.org/bugzilla/>
2011-11-23 19:39 ` 3dw4rd at verizon dot net
2021-01-19 13:57 ` jakub at gcc dot gnu.org
2021-01-19 13:58 ` jakub at gcc dot gnu.org
2021-01-20 9:37 ` jakub at gcc dot gnu.org
2021-07-22 21:57 ` pinskia at gcc dot gnu.org
2021-07-22 21:57 ` pinskia at gcc dot gnu.org
2021-07-22 21:58 ` pinskia at gcc dot gnu.org [this message]
2021-07-22 23:16 ` pinskia at gcc dot gnu.org
2022-07-23 10:54 ` egallager at gcc dot gnu.org
2022-10-03 16:41 ` pinskia at gcc dot gnu.org
2022-12-01 8:41 ` egallager at gcc dot gnu.org
[not found] <20001111043600.772.jsm28@gcc.gnu.org>
2005-03-31 7:26 ` pinskia at gcc dot gnu dot org
2005-04-03 18:56 ` pinskia at gcc dot gnu dot org
2005-09-09 12:38 ` rguenth at gcc dot gnu dot org
2005-09-09 15:41 ` joseph at codesourcery dot com
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-772-4-Ss0eZJxS7B@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).