http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51033
--- Comment #26 from Ramana Radhakrishnan <ramana at gcc dot gnu.org>
2012-06-14 11:22:26 UTC ---
(In reply to comment #23)
> (In reply to comment #21)
> > What does it mean "exercise the backend a lot"? Do you mean it takes a lot
> > of
> > time?
>
> I think so.
>
> > I haven't looked at the tests, but I think it is not a problem to run
> > compile-only tests with both gcc and g++.
>
> compile-time tests are not always sufficient.
>
> The __builtin_shuffle tests are spread in:
> gcc.dg{,/torture}
> gcc.target/{i386,powerpc}
> gcc.c-torture/{compile,execute}
>
> I assume the tests in gcc.dg can move to c-c++-common. The target tests should
> stay in target. Not sure about gcc.c-torture.
>
> But one interesting thing to test is if the front-end passes the arguments as
> constants and thus the backend can use specialized code instead of the slow
> generic one. And this kind of test seems necessarily target-specific. Bah, I
> guess I shouldn't ask for too much and moving the gcc.dg tests would be
> enough.
Patch posted for comments here :
http://gcc.gnu.org/ml/gcc-patches/2012-06/msg00903.html
