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: Reorganizing -flto and -fwhopr command line options (Was Re: WHOPR partitioning, take 2)


On Tue, Oct 5, 2010 at 15:20, Jan Hubicka <hubicka@ucw.cz> wrote:

> Basically we now have
> 1) -flto for LTO (no ltrans streaming)
> 2) -fwhopr for WHOPR with no parallelizm (equivalent of -fwhopr=1)
> 3) -fwhopr=0 for WHOPR with no parallelizm and no temporary makefile
> 4) -fwhopr=n for WHOPR, temporary makefile and parallelizm
> 5) -fwhopr=jobserv for automatic parallelizm, but we need those + rules in GCC.
>
> I think we want -flto to default to WHOPR and I think it makes sense to adopt
> =n and =jobserv syntax. ÂI would love it to default to -fwhopr=jobserv but until
> it produces warning about missing + rules (and need them), I think we are stuck.
> We might get fancy and default to 2 or 4 claiming that most developer workstations
> are 2 or 4 core these days, but I guess we will just make it to default to -fwhopr=1?
>
> I wonder if we want to support -flto=0 in the sense of 1) or 4).

I was under the impression that -flto=0 would mean (1).  You want
-flto to always mean -fwhopr?  Any particular reason?  For
small/medium TUs, whopr seems overkill.

The rest looks fine.


Diego.


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