This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch, gfortran] pr22570 and related issues.
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: François-Xavier Coudert <fxcoudert at gmail dot com>
- Cc: Paul Thomas <paulthomas2 at wanadoo dot fr>, fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Thu, 28 Jul 2005 15:47:03 -0700
- Subject: Re: [patch, gfortran] pr22570 and related issues.
- References: <42E677B0.30200@wanadoo.fr> <19c433eb050727143345bc7088@mail.gmail.com>
On Wed, Jul 27, 2005 at 11:33:57PM +0200, François-Xavier Coudert wrote:
> > In the longer run, there might be some advantage in
> > modifying the NIST suite to run as part of the gfortran testsuite. The
> > work required to do this would be perspiration rather than inspiration
> > based. If it is thought to be useful, we could look into this,
> > although there are no promises on the timescale.
>
> NIST cannot be included in the gfortran testsuite (and I don't think
> we would want it, in any case), but we can arrange for it to be run
> regularly.
If you come up with an easy way to include the NIST suite in GCC testing
(although without having the tests themselves in the GCC testsuite), let
us know; I'd add it to my nightly testing on powerpc64-linux. Could it
be done like JACKS and MAUVE are for Java?
Janis