This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [PATCH, PR16464] testsuite: account for fortran loop-constructs
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Bernhard Reutner-Fischer <rep dot dot dot nop at gmail dot com>
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, billingd at gcc dot gnu dot org
- Date: Fri, 2 Mar 2012 15:05:35 +0100
- Subject: Re: [PATCH, PR16464] testsuite: account for fortran loop-constructs
- References: <1330696891-32461-1-git-send-email-rep.dot.nop@gmail.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Mar 02, 2012 at 03:01:31PM +0100, Bernhard Reutner-Fischer wrote:
> PR testsuite/16464 notes that some g77/*.f that contain loops were not
> compiled with loop flags.
> Compiling only testcases with loop optimization that contain
> "endfor/enddo" will lead to ~25% fewer tests (some 30000 instead of
> previously 40000).
>
> Testing in progess, ok if this completes successfully?
There are tons of other loop constructs in Fortran, so I don't think this is
a good idea.
> 2012-03-02 Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
>
> PR testsuite/16464
> * lib/gfortran-dg.exp (gfortran-dg-runtest): Depend options
> on weather the testcase is just preprocessed/compiled or
> contains loop statements.
Jakub