This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/52075] OpenMP atomic update failing if -fbounds-check specified
- From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 09 Dec 2014 20:52:58 +0000
- Subject: [Bug fortran/52075] OpenMP atomic update failing if -fbounds-check specified
- Auto-submitted: auto-generated
- References: <bug-52075-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52075
Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |Joost.VandeVondele at mat dot ethz
| |.ch
Resolution|--- |FIXED
--- Comment #5 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
reproduces for me gcc version 4.8.3 20140315 (prerelease) [gcc-4_8-branch
revision 208588] and gcc version 4.9.2 20140917 (prerelease) [gcc-4_9-branch
revision 215328] (GCC), but not with trunk.
> gfortran -fopenmp -fbounds-check t.f90 ; for i in `seq 1 5` ; do ./a.out ; done
FAIL - X( 633 ) == 14 (expected 15 )
STOP 1
FAIL - X( 101 ) == 14 (expected 15 )
STOP 1
FAIL - X( 292 ) == 14 (expected 15 )
STOP 1
I strongly suspect that this was fixed as part of PR63938 (backported also to
4.8, 4.9 ). In fact, an updated 4.8 branch is fine.
Thanks for the report, too bad this was overlooked for so long.