public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60221] [4.7/4.8 Regression] gcc -fexceptions generates unnecessary cleanup code
Date: Fri, 21 Feb 2014 09:16:00 -0000 [thread overview]
Message-ID: <bug-60221-4-yCufH5uKVP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60221-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60221
--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 20 Feb 2014, redlizard at redlizard dot nl wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60221
>
> --- Comment #6 from Ruud Koolen <redlizard at redlizard dot nl> ---
> This fix solves my original problem. Resolved, as far as I'm concerned.
>
> Will this fix also be applied to 4.7 and 4.8?
After some time and no problems show up, yes. I expect it to hit
4.8.3 at least, not sure about 4.7.
next prev parent reply other threads:[~2014-02-21 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 3:46 [Bug c/60221] New: " redlizard at redlizard dot nl
2014-02-16 4:55 ` [Bug middle-end/60221] " pinskia at gcc dot gnu.org
2014-02-17 12:32 ` [Bug middle-end/60221] [4.7/4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2014-02-17 15:41 ` jakub at gcc dot gnu.org
2014-02-18 10:41 ` rguenth at gcc dot gnu.org
2014-02-20 9:01 ` rguenth at gcc dot gnu.org
2014-02-20 22:09 ` [Bug middle-end/60221] [4.7/4.8 " redlizard at redlizard dot nl
2014-02-21 9:16 ` rguenther at suse dot de [this message]
2014-02-25 10:47 ` rguenth at gcc dot gnu.org
2014-02-25 10:48 ` [Bug middle-end/60221] [4.7 " rguenth at gcc dot gnu.org
2014-03-09 19:00 ` pinskia at gcc dot gnu.org
2014-05-23 8:27 ` 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-60221-4-yCufH5uKVP@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).