From: Teresa Johnson <tejohnson@google.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
David Li <davidxl@google.com>, Jan Hubicka <hubicka@ucw.cz>,
Steven Bosscher <stevenb.gcc@gmail.com>
Subject: Re: [PATCH i386] Enable -freorder-blocks-and-partition
Date: Tue, 19 Nov 2013 22:10:00 -0000 [thread overview]
Message-ID: <CAAe5K+Ub_OyxhXuZpEMeToGtUobTGjR98wVL6VNHk_nh_AH9Yw@mail.gmail.com> (raw)
In-Reply-To: <8738msxg2o.fsf@tassilo.jf.intel.com>
On Tue, Nov 19, 2013 at 1:00 PM, Andi Kleen <andi@firstfloor.org> wrote:
> Teresa Johnson <tejohnson@google.com> writes:
>
>> This patch enables -freorder-blocks-and-partition by default for x86
>> at -O2 and up. It is showing some modest gains in cpu2006 performance
>> with profile feedback and -O2 on an Intel Westmere system. Specifically,
>> I am seeing consistent improvements in 401.bzip2 (1.5-3%), 483.xalancbmk
>> (1.5-3%), and 453.povray (2.5-3%), and no apparent regressions.
>
> One thing that worries me is what this will do to profilers.
>
> I had to hack some assembler code using out of line sections
> to able to handle the libunwind based perf dwarf unwinder.
>
> My understanding is that these out of line sections can be
> only described properly in dwarf3, and there's still some
> dwarf2 based unwinder code around.
>
> So this may cause problems with profiling and debugging.
>
> It's probably still a good idea, just may need some extra
> care.
>
> -Andi
Sri has approval for a patch that should address this by giving the
split cold sections a label. It should go in today as well:
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg02143.html
Thanks,
Teresa
>
> --
> ak@linux.intel.com -- Speaking for myself only
--
Teresa Johnson | Software Engineer | tejohnson@google.com | 408-460-2413
prev parent reply other threads:[~2013-11-19 21:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 15:17 Teresa Johnson
2013-11-19 16:31 ` Jan Hubicka
2013-11-19 18:23 ` Teresa Johnson
2013-11-19 19:32 ` Jeff Law
2013-11-20 1:55 ` Teresa Johnson
[not found] ` <CAObPJ3OZHvET=QNmNtx9ZjaHZk=GhokWjoF2njr5mgwcv2ogDA@mail.gmail.com>
2013-11-28 16:34 ` Jan Hubicka
2013-12-02 15:16 ` Teresa Johnson
2013-12-02 16:17 ` Jeff Law
2013-12-02 16:53 ` Martin Liška
2013-12-11 9:21 ` Martin Liška
2013-12-12 5:51 ` Teresa Johnson
2013-12-12 20:54 ` Jan Hubicka
2013-12-13 1:13 ` Jan Hubicka
[not found] ` <CAObPJ3MLrWsTwK-23ienktyASO9YLvAXMNKUxVm3v+KC=5JzOA@mail.gmail.com>
2013-12-15 22:19 ` Martin Liška
2013-12-17 15:09 ` Teresa Johnson
2013-12-20 6:19 ` Teresa Johnson
2014-02-11 22:21 ` Teresa Johnson
2014-02-14 18:50 ` Teresa Johnson
2013-11-19 22:05 ` Andi Kleen
2013-11-19 22:10 ` Teresa Johnson [this message]
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=CAAe5K+Ub_OyxhXuZpEMeToGtUobTGjR98wVL6VNHk_nh_AH9Yw@mail.gmail.com \
--to=tejohnson@google.com \
--cc=andi@firstfloor.org \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--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).