This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Come up with -flto=auto option.

From: Jeff Law <law at redhat dot com>
To: Jan Hubicka <hubicka at ucw dot cz>, Martin Liška <mliska at suse dot cz>
Cc: gcc-patches at gcc dot gnu dot org, Michael Matz <matz at suse dot de>, Richard Biener <richard dot guenther at gmail dot com>
Date: Tue, 23 Jul 2019 07:09:30 -0600
Subject: Re: [PATCH] Come up with -flto=auto option.
References: <95f20c0a-81a3-2319-326b-3c5baf71e2d1@suse.cz> <20190723092040.czs64os2qymax7sq@kam.mff.cuni.cz>

On 7/23/19 3:20 AM, Jan Hubicka wrote:
>> Hi.
>>
>> As we as openSUSE started using -flto, I see it very handy to have
>> an option value that will automatically detect number of cores
>> that can be used for parallel LTRANS phase.
>>
>> Thoughts?
> Hi,
> great you found time to make this. It should become the default for
> -flto IMO.
I was going to hack it into the rpm configury bits since we have access
to the # cores there.  But an auto-selector within GCC is even better.

BTW, isn't this all going to wreck havoc with reproducible builds since
partitioning can affect code generation?  That's one of our open
questions...

Jeff

Follow-Ups:
- Re: [PATCH] Come up with -flto=auto option.
  - From: Richard Biener
- Re: [PATCH] Come up with -flto=auto option.
  - From: Michael Matz

References:
- [PATCH] Come up with -flto=auto option.
  - From: Martin Liška
- Re: [PATCH] Come up with -flto=auto option.
  - From: Jan Hubicka

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]