From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Kevin Buettner <kevinb@redhat.com>,
gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 8.2 release 2018-08-21 status update
Date: Fri, 24 Aug 2018 19:52:00 -0000 [thread overview]
Message-ID: <23af714e-9fd0-f86c-e1f1-66f4931d3a20@redhat.com> (raw)
In-Reply-To: <de654842f8b1b186fce915fcc94d4d82@polymtl.ca>
On 08/24/2018 08:14 PM, Simon Marchi wrote:
> On 2018-08-24 14:35, Pedro Alves wrote:
>> Unless I'm wrong that
>> -freorder-blocks-and-partition is on by default in GCC 8 already?
>
> Looking at gcc/doc/invoke.texi, apparently it's been enabled for -O2/-O3 for some time and more recently -Os. You can check whether it is enabled with:
>
> Â gcc -Q -v --help 2>/dev/null | grep reorder-blocks-and-partition
>
> I see it as disabled by default and enabled if I add -O2, with different gcc versions between 5.4.0 and 8.2.0. So it doesn't seem to have changed recently. Maybe what changed is that gcc 8 partitions more aggressively? Or it's just that gcc developers tend to debug -O2 builds? I have no idea.
Here's what Jakub Jelinek had to say about it:
<palves> is -freorder-blocks-and-partition on by default in any gcc release yet?
<jakub_> palves: yes, in gcc 8
<jakub_> palves: for older releases I believe it has been enabled, but due to a bug actually disabled later on, unless -fprofile-use was used
<jakub_> palves: "-freorder-blocks-and-partition, a pass splitting function bodies into hot and cold regions, is now enabled by default at -O2 and higher for x86 and x86-64." is in gcc.gnu.org/gcc-8/changes.html
<jakub_> palves: it was added for -fprofile-use initially, and its test coverage was using usually explicit -freorder-blocks-and-partition
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-08-24 19:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 17:51 Joel Brobecker
2018-08-21 18:33 ` Kevin Buettner
2018-08-21 19:02 ` Simon Marchi
2018-08-21 20:17 ` Simon Marchi
2018-08-21 20:54 ` Joel Brobecker
2018-08-22 16:07 ` Simon Marchi
2018-08-22 17:38 ` Simon Marchi
2018-08-22 18:03 ` Stan Cox
2018-08-22 18:09 ` Simon Marchi
2018-08-21 20:55 ` Joel Brobecker
2018-08-21 21:29 ` Simon Marchi
2018-08-23 17:56 ` Pedro Alves
2018-08-24 18:01 ` Pedro Alves
2018-08-23 18:37 ` Simon Marchi
2018-08-23 22:41 ` Kevin Buettner
2018-08-24 18:35 ` Pedro Alves
2018-08-24 19:15 ` Simon Marchi
2018-08-24 19:52 ` Pedro Alves [this message]
2018-08-24 3:57 ` Kevin Buettner
2018-08-25 5:41 ` Kevin Buettner
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=23af714e-9fd0-f86c-e1f1-66f4931d3a20@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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