From: Andi Kleen <ak@linux.intel.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
Andrew Pinski <pinskia@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Malcolm <dmalcolm@redhat.com>
Subject: Re: [PATCH] Force rtl templates to be inlined
Date: Tue, 02 Sep 2014 16:52:00 -0000 [thread overview]
Message-ID: <20140902165244.GH25920@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAFiYyc0XzKwgkbf+S=3a4sMa7HrO5tbngqaFUrUVz8v7+vatMQ@mail.gmail.com>
> Or we simply should make -finline work at -O0 (I suppose it might already
> work?) and use it.
Yes that's probably better. There are more hot inlines in the stage 1 profile
(like wi::storage_ref or vec::length)
I suspect with the ongoing C++'ification that will get worse.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-09-02 16: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 [this message]
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
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=20140902165244.GH25920@tassilo.jf.intel.com \
--to=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).