--- Comment #4 from bgarvin at acm dot org 2010-02-02 01:43 ---
(In reply to comment #3)
> >torture
> For the torture test you can set the TORTURE OPTIONS separately and let the
> testsuite do the rest.
>
Yeah, that's what I meant. Thanks for the clarification and sorry about the
inva
--- Comment #3 from pinskia at gcc dot gnu dot org 2010-02-02 01:36 ---
>torture
For the torture test you can set the TORTURE OPTIONS separately and let the
testsuite do the rest.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42933
--- Comment #2 from bgarvin at acm dot org 2010-02-02 01:30 ---
(In reply to comment #1)
> Well RUNTESTFLAGS is really only useful for options which change the ABI and
> have a multilib. Like -fPIC/-m64/-m32, etc. -std=c++0x changes the input
> language which is used so therefor change
--- Comment #1 from pinskia at gcc dot gnu dot org 2010-02-02 01:14 ---
Well RUNTESTFLAGS is really only useful for options which change the ABI and
have a multilib. Like -fPIC/-m64/-m32, etc. -std=c++0x changes the input
language which is used so therefor changes the whole testsuite.
