This is the mail archive of the
mailing list for the GCC project.
Re: Should bootstrap-O3 be the default for building/testing GCC?
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Gary Funck <gary at intrepid dot com>
- Cc: GCC List <gcc at gcc dot gnu dot org>, Nenad Vukicevic <nenad at intrepid dot com>
- Date: Fri, 8 Jan 2016 10:52:01 +0100
- Subject: Re: Should bootstrap-O3 be the default for building/testing GCC?
- Authentication-results: sourceware.org; auth=none
- References: <20151224144033 dot GC24093 at intrepid dot com>
On Thu, Dec 24, 2015 at 3:40 PM, Gary Funck <firstname.lastname@example.org> wrote:
> Currently, the default optimization level when building,
> bootstrapping GCC is -O2.
> We routinely build with --with-build-config='bootstrap-debug bootstrap-O3'
> because we want to verify that our UPC changes don't affect the
> compiler when built with full optimizations. We also build
> with --enable-checking=all.
> Since most developers probably build/test GCC with the default -O2 options,
> we fairly often run into -O3 related issues when building GCC.
> Enough so that we're considering just using the default -O2 settings.
> I'm wondering if there might be benefit in changing the current defaults
> to use -O3 instead? Or perhaps have the configure infrastructure
> determine that the build is for a development version of GCC
> and set the flags and options accordingly?
> Somewhat related: has anyone recently determined whether a GCC built
> with -O3 is generally faster/smaller than one built at -O2?
-O3 will just result in larger code IIRC. You get benefits from
both size and performance-wise (profiledbootstrap also enables most of what
So no, we don't want to change the defaults.
> - Gary