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: [lto] Run some testsuites with LTO if it's available


On Tue, May 19, 2009 at 13:29, Janis Johnson <janis187@us.ibm.com> wrote:
> On Tue, 2009-05-19 at 12:37 -0400, Diego Novillo wrote:
>> Janis,
>>
>> Does this look OK for supporting LTO only when it's available?
>> Initially I wanted to always add -flto if it was available, but
>> there may be other reasons why a testsuite would not want LTO, so
>> it needs to be merged in by each .exp file.
>
> Yes, it looks OK assuming that you want to run all torture tests
> three times as much as they are currently run.

Thanks.  Yes, it's OK for now to run them in all possible
combinations.  For the mainline merge my idea is to just append {-O0
-flto} {-O2 -flto} {-O0 -fwhopr} {-O2 -fwhopr} to the result of the
set-torture-options call.  This will only add 4 more sets of flags
instead of 3x.

> for now in the LTO branch but won't later for mainline. ÂEventually
> there should be a set of LTO-specific tests that are run always

Yes, those would be the tests in gcc.dg/lto and g++.dg/lto

> and perhaps some torture tests that always use it, and others should
> use the LTO options when the user asks for them, through the
> environment or site.exp or .dejagnurc (we need a common convention
> for stuff like that).

Sounds good.


Thanks.  Diego.


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