This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/86417] [9 Regression] FAIL: libgomp.fortran/alloc-comp-3.f90 -O0 (test for excess errors)
- From: "janus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 06 Jul 2018 10:55:58 +0000
- Subject: [Bug fortran/86417] [9 Regression] FAIL: libgomp.fortran/alloc-comp-3.f90 -O0 (test for excess errors)
- Auto-submitted: auto-generated
- References: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86417
--- Comment #5 from janus at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #4)
> The idea of the warning is to ensure that we have
> Location information everywhere, and that patches
> Which do not correctly set the location should cause
> something visible during testing. We do not have this for
> release.
Thanks for the explanation. Makes sense.
Do you have any idea what might have caused the regression?
> We should take care to always regression test libgomp.fortran
> as well...
Yes, I finally got into this habit, after repeatedly breaking libgomp tests
with my patches without noticing it.
I also tried to document how to do this at the bottom of this wiki page:
https://gcc.gnu.org/wiki/TestCaseWriting
It took me a while to figure out how to actually run the Fortran subset of the
libgomp suite (which is not very well documented, or I'm too stupid to find
it).