Re: [PATCH, PR16464] testsuite: account for fortran loop-constructs

2012-03-02 Thread Richard Guenther
On Fri, Mar 2, 2012 at 3:25 PM, Bernhard Reutner-Fischer wrote: > On Mar 2, 2012 3:09 PM, "Richard Guenther" > wrote: >> >> On Fri, Mar 2, 2012 at 3:05 PM, Jakub Jelinek wrote: >> > On Fri, Mar 02, 2012 at 03:01:31PM +0100, Bernhard Reutner-Fischer >> > wrote: >> >> PR testsuite/16464 notes that

Re: [PATCH, PR16464] testsuite: account for fortran loop-constructs

2012-03-02 Thread Richard Guenther
On Fri, Mar 2, 2012 at 3:05 PM, Jakub Jelinek wrote: > 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 >>

Re: [PATCH, PR16464] testsuite: account for fortran loop-constructs

2012-03-02 Thread Jakub Jelinek
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 3 in

[PATCH, PR16464] testsuite: account for fortran loop-constructs

2012-03-02 Thread Bernhard Reutner-Fischer
Hi, 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 3 instead of previously 4). Testing in progess, ok if this completes success