From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, Andi Kleen <ak@linux.intel.com>,
Steven Bosscher <stevenb.gcc@gmail.com>,
Andrew Pinski <pinskia@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Malcolm <dmalcolm@redhat.com>, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH] Force rtl templates to be inlined
Date: Thu, 04 Sep 2014 18:52:00 -0000 [thread overview]
Message-ID: <20140904185225.GC20099@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAFiYyc0Yx6RdpqTztxdqqDWYw=o0RwRPGwps6O81mU5OK7ee9w@mail.gmail.com>
> On Thu, Sep 4, 2014 at 5:58 AM, Andi Kleen <andi@firstfloor.org> wrote:
> >>
> >> Anyway, removing !optimize checks in favor of flag_no_inline checks
> >> and initializing that properly is a cleanup as well.
> >
> > Patch looks good to me.
>
> Unfortunately it doesn't pass bootstrap (inline-summary re-use
> between IPA passes is a maze...). So I need to tweak it more
> (pushed back for now).
From a quick glance it looks resonable thing to do.
I can fix the summary issues after returning from trip this Sunday.
Honza
>
> Richard.
>
> > -Andi
next prev parent reply other threads:[~2014-09-04 18:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 7:05 Andi Kleen
2014-09-02 7:09 ` Andrew Pinski
2014-09-02 7:20 ` Andi Kleen
2014-09-02 7:22 ` Andrew Pinski
2014-09-02 8:37 ` Steven Bosscher
2014-09-02 8:42 ` pinskia
2014-09-02 8:43 ` Richard Biener
2014-09-02 16:52 ` Andi Kleen
2014-09-03 9:50 ` Richard Biener
2014-09-04 3:58 ` Andi Kleen
2014-09-04 13:02 ` Richard Biener
2014-09-04 18:52 ` Jan Hubicka [this message]
2014-09-03 9:52 ` Richard Biener
2014-09-02 14:59 ` David Malcolm
2014-09-02 17:50 ` Andi Kleen
2014-09-04 20:07 ` [PATCH] Add XINSN macro and use it within NEXT_INSN/PREV_INSN (was Re: [PATCH] Force rtl templates to be inlined) David Malcolm
2014-09-04 20:46 ` Jakub Jelinek
2014-09-04 21:23 ` David Malcolm
2014-09-05 18:41 ` Jeff Law
2014-09-05 18:32 ` Jeff Law
2014-09-05 18:45 ` Jeff Law
2014-09-05 19:05 ` David Malcolm
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=20140904185225.GC20099@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=stevenb.gcc@gmail.com \
/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).