This is the mail archive of the gcc@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]

[lto] Enabling LTO in selected testsuite directories


On the LTO branch, I am brute-forcing LTO compilation on all the
testsuite directories.  This causes many spurious failures because we
are not going to support LTO compiles on everything.  For instance,
LTO is not supported for fortran, java, ada, mudflap.  Also, for some
tests like pch, the tests fail trivially because of assembly
miscomparison (due to the LTO sections).

I am trying to come up with a generic mechanism that can be used in
individual .exp files so they can decide whether to test the two LTO
modes.  In terms of dg.exp, it would mean adding 3 or 4 new entries to
DG_TORTURE_OPTIONS ({-O0 -flto}, {-O2 -flto}, {-O0 -fwhopr}, {-O2
-fwhopr}).

Do you have any suggestion on how I could implement that?


Thanks.  Diego.


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