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 tree-optimization/40874] Function object abstraction penalty with inline functions.
Date: Wed, 29 Jul 2009 10:57:00 -0000 [thread overview]
Message-ID: <20090729105702.28218.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40874-501@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from rguenther at suse dot de 2009-07-29 10:57 -------
Subject: Re: Function object abstraction penalty
with inline functions.
On Wed, 29 Jul 2009, jamborm at gcc dot gnu dot org wrote:
> ------- Comment #13 from jamborm at gcc dot gnu dot org 2009-07-29 10:16 -------
> (In reply to comment #12)
> > ... at least scheduling FRE is still on the list of possible things
> > todo (can you check if that fixes 3713 as well?)
> >
>
> No, it doesn't (unlike the testcase above, for which FRE is enough).
> We have to remove the if-statement in (foo is a function):
>
> p$__pfn_25 = foo;
> D.1739_3 = (int) p$__pfn_25;
> D.1740_4 = D.1739_3 & 1;
> if (D.1740_4 != 0)
> goto <bb 3>;
> else
> goto <bb 4>;
>
> Not even FRE combined with a subsequent fwprop (in their current form)
> can make this happen :-/
FRE has to be teached the & 1 simplification via looking through the
int cast.
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40874
next prev parent reply other threads:[~2009-07-29 10:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 15:06 [Bug c++/40874] New: Function object abstraction penalty dave at boost-consulting dot com
2009-07-27 15:36 ` [Bug tree-optimization/40874] " pinskia at gcc dot gnu dot org
2009-07-27 15:45 ` [Bug tree-optimization/40874] Function object abstraction penalty with inline functions pinskia at gcc dot gnu dot org
2009-07-27 16:26 ` dave at boost-consulting dot com
2009-07-27 17:57 ` paolo dot carlini at oracle dot com
2009-07-28 11:23 ` rguenth at gcc dot gnu dot org
2009-07-28 18:42 ` dave at boost-consulting dot com
2009-07-28 19:39 ` paolo dot carlini at oracle dot com
2009-07-28 21:33 ` jamborm at gcc dot gnu dot org
2009-07-29 8:06 ` rguenth at gcc dot gnu dot org
2009-07-29 8:06 ` rguenther at suse dot de
2009-07-29 8:09 ` hubicka at ucw dot cz
2009-07-29 8:12 ` rguenther at suse dot de
2009-07-29 10:17 ` jamborm at gcc dot gnu dot org
2009-07-29 10:57 ` rguenther at suse dot de [this message]
[not found] <bug-40874-4@http.gcc.gnu.org/bugzilla/>
2011-05-23 14:51 ` rguenth at gcc dot gnu.org
2011-05-23 15:09 ` 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=20090729105702.28218.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).