public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/28850] missed call -> jmp transformation; redundant unwind stuff with empty finally
Date: Fri, 25 Aug 2006 21:59:00 -0000 [thread overview]
Message-ID: <20060825215918.2871.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28850-7667@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pinskia at gcc dot gnu dot org 2006-08-25 21:59 -------
(In reply to comment #1)
> It's not entirely clear from your report, but this looks like a bug of PR13397?
No it is not fully related. One of the problems is that we don't remove empty
finnally blocks.
Reduced testcase for that problem:
struct bomber
{
~bomber() { }
};
int g(void);
int f(void)
{
bomber a;
g();
}
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2006-08-25 21:59:14
date| |
Summary|missed call -> jmp |missed call -> jmp
|transformation; redundant |transformation; redundant
|unwind stuff. |unwind stuff with empty
| |finally
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28850
next prev parent reply other threads:[~2006-08-25 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 20:40 [Bug tree-optimization/28850] New: missed call -> jmp transformation; redundant unwind stuff pluto at agmk dot net
2006-08-25 21:52 ` [Bug tree-optimization/28850] " rguenth at gcc dot gnu dot org
2006-08-25 21:59 ` pinskia at gcc dot gnu dot org [this message]
2006-08-26 10:07 ` [Bug tree-optimization/28850] missed call -> jmp transformation; redundant unwind stuff with empty finally rguenth at gcc dot gnu dot org
2009-03-29 13:32 ` hubicka at gcc dot gnu dot org
[not found] <bug-28850-4@http.gcc.gnu.org/bugzilla/>
2011-06-22 22:05 ` pluto at agmk dot net
2021-12-25 6:12 ` pinskia 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=20060825215918.2871.qmail@sourceware.org \
--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).