This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Fix ACATS failures in GCC 3.4
> Hi Eric, thanks for catching this, we now get a clean ACATS run on HEAD
> at least on x86-linux :).
Hi Laurent. Yes, this was sort of the ultimate goal (well, primarily on the
3.4 branch I'd say), although one could argue that I rushed a bit to check
the patch in, in light of Roger's comment :-)
> If I change testsuite/ada/acats/run_all.sh variable gccflags to "-O3"
> I get 10 failures:
>
> c24211a c94008c cc70a01 cxg2006 cxg2007
> cxg2008 cxg2018 cxg2019 cxg2020 cxg2021
>
> c24211a and cc70a01 are unexpected run time exceptions,
> the cxg are various floating point "accuracy" problems,
> might be trickier to investigate, I'll try reducing
> this weekend.
>
> If I use "-O3 -funroll-all-loops" I get 6 additional
> failures (total 16), all backend ICEs:
>
> cxa5011 cxg2003 cxg2004 cxg2011 cxg2014
> cxh1001
>
> Since failures at high optimization seem to be a superset
> of failures at no optimization (it has always been the case for my past
> year testing), may be it makes sense to choose "-O3" as the new ACATS
> default after we've confirmed that these are real bugs (and not ACATS
> bugs - these happens :).
I think that Arnaud is right, -O2 might be preferable here. What would be
interesting is to run ACATS at -O2 on the 3.4 branch.
--
Eric Botcazou