compile time testsuite [Re: alias slowdown?]
Richard Guenther
richard.guenther@gmail.com
Tue Nov 21 14:55:00 GMT 2006
On 11/21/06, Benjamin Kosnik <bkoz@redhat.com> wrote:
>
> oops I got Dan's email wrong. Sorry.
>
> > Yup, I like this idea. I would only avoid adding .ii files, as they are
> > very brittle. I use this sandbox:
> >
> > DLV (Gerald's)
> > MICO (www.mico.org)
> > cc1-i-files (.i and .ii files from a full bootstrap)
> > tramp3d (Richard G's)
> > SPEC2000
> > two .ii files from Bugzilla PRs (cpgram.ii from 15855 and rt-3.4.ii from
> > some other PR I can't remember ATM)
> >
> > With the exception of DLV and SPEC2000, we could probably add most of
> > them to the check-compile testsuite. I don't know if Gerald would be
> > able to allow DLV to be included.
>
> It seems as if you, Dan, and Andrew are all using different test cases!
> No wonder there is so much confusion....
>
> I suppose for SPEC and DLV you could do the same thing that Cygnus used
> to do for the dejagnu testing of Perennial and Plum Hall... you could
> just require links and or env variables, and if the required
> links/directories/variables were not set, you'd skip it.
>
> Not great, but sufficient. Again, I think getting something going that
> works is more important than getting something super-elegant and shiny
> in.
>
> I'm not quite sure how to go about automating the i and ii file
> generation. This seems difficult.
What helps to get the testcases independent of system headers and libstdc++
is to run the uninclude script over the .i/.ii files so you get a
.c/.cpp file back
which more likely supports a wide range of compilers, hosts and
libstdc++ versions.
Richard.
More information about the Gcc
mailing list