[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-08-22 Thread rguenth at gcc dot gnu dot org
--- Comment #9 from rguenth at gcc dot gnu dot org 2008-08-22 15:02 --- *** Bug 36983 has been marked as a duplicate of this bug. *** -- rguenth at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-06 Thread hjl dot tools at gmail dot com
--- Comment #8 from hjl dot tools at gmail dot com 2008-03-06 22:03 --- This is a known issue with mgrid. The absolute tolerance is too small. After increasing absolute tolerance from 1.0e-12 to 1.0e-11, the miscomparison is gone. -- hjl dot tools at gmail dot com changed:

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-05 Thread fxcoudert at gcc dot gnu dot org
-- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added CC||fxcoudert at gcc dot gnu dot |

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-02 Thread rguenth at gcc dot gnu dot org
--- Comment #7 from rguenth at gcc dot gnu dot org 2008-03-02 11:00 --- Note the COND_EXRPs will be lowered to control-flow while the MAX_EXPRs will retain a single BB. Still, on i686 the exactly same inner loop IL is created. And btw I don't see mgrid miscomparing on our tester that r

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-02 Thread rguenth at gcc dot gnu dot org
--- Comment #6 from rguenth at gcc dot gnu dot org 2008-03-02 10:31 --- The foldings look legit. I wonder in which dump there starts to be a real difference? I suppose maybe the vectorizer now can do work if not faced with a COND_EXPR. -- rguenth at gcc dot gnu dot org changed:

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-01 Thread kargl at gcc dot gnu dot org
--- Comment #5 from kargl at gcc dot gnu dot org 2008-03-02 01:33 --- (In reply to comment #4) > I got > > Running 172.mgrid ref base o2 default > *** Miscompare of mgrid.out, see > /export/gnu/import/rrs/spec/2000/spec/benchspec > /CFP2000/172.mgrid/run/0002/mgrid.out.mis > Inval

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-01 Thread hjl dot tools at gmail dot com
--- Comment #4 from hjl dot tools at gmail dot com 2008-03-02 01:11 --- I got Running 172.mgrid ref base o2 default *** Miscompare of mgrid.out, see /export/gnu/import/rrs/spec/2000/spec/benchspec /CFP2000/172.mgrid/run/0002/mgrid.out.mis Invalid run; unable to continue. If you w

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-01 Thread tobi at gcc dot gnu dot org
--- Comment #3 from tobi at gcc dot gnu dot org 2008-03-01 23:15 --- I checked the code leading up to this, and if I didn't miss a codepath, stride will always be of type gfc_array_index_type, so I'm inclined to believe that the bug, if any, is in fold. It is of course possible that fol

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-01 Thread kargl at gcc dot gnu dot org
--- Comment #2 from kargl at gcc dot gnu dot org 2008-03-01 22:59 --- Define "miscompiles"? Remove -ffast-math? Add -fbounds-check? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35418

[Bug fortran/35418] [4.4 Regression]: Revision 132592 miscompiles 172.mgrid

2008-03-01 Thread hjl dot tools at gmail dot com
--- Comment #1 from hjl dot tools at gmail dot com 2008-03-01 22:50 --- The code looks like SUBROUTINE RESID(U,V,R,N,A) INTEGER N REAL*8 U(N,N,N),V(N,N,N),R(N,N,N),A(0:3) INTEGER I3, I2, I1 DO 600 I3=2,N-1 DO 600 I2=2,N-1 DO 600 I1=2,N-1 N is