[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2023-07-07 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

Richard Biener  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
   Target Milestone|10.5|11.0

--- Comment #15 from Richard Biener  ---
fixed.

[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2022-06-28 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|10.4|10.5

--- Comment #14 from Jakub Jelinek  ---
GCC 10.4 is being released, retargeting bugs to GCC 10.5.

[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2021-04-08 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|10.3|10.4

--- Comment #13 from Richard Biener  ---
GCC 10.3 is being released, retargeting bugs to GCC 10.4.

[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2020-07-23 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|10.2|10.3

--- Comment #12 from Richard Biener  ---
GCC 10.2 is released, adjusting target milestone.

[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2020-05-07 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|10.0|10.2

--- Comment #11 from Jakub Jelinek  ---
GCC 10.1 has been released.

[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2019-08-26 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

--- Comment #10 from Thomas Koenig  ---
Author: tkoenig
Date: Mon Aug 26 20:05:32 2019
New Revision: 274937

URL: https://gcc.gnu.org/viewcvs?rev=274937=gcc=rev
Log:
2019-08-26  Thomas Koenig  

PR fortran/91390
PR fortran/91473
* frontend-passes.c (gfc_check_externals): Make
gfc_errors_to_warnings conditional on -fallow-argument-mismatch.
* invoke.texi: Document -fallow-argument-mismatch.
* lang.opt: Add -fallow-argument-mismatch.

2019-08-26  Thomas Koenig  

PR fortran/91390
PR fortran/91473
* gfortran.dg/used_before_typed_4.f90: Change warning to error.
* gfortran.dg/argument_checking_20.f90: New test.


Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/frontend-passes.c
trunk/gcc/fortran/invoke.texi
trunk/gcc/fortran/lang.opt
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/used_before_typed_4.f90

[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2019-08-22 Thread seurer at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

--- Comment #9 from seurer at gcc dot gnu.org ---
Note pr91524

[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2019-08-20 Thread seurer at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

--- Comment #8 from seurer at gcc dot gnu.org ---
So for 481.wrf in cpu2006 add this to the config:

FPORTABILITY = -std=legacy

Add the same for 178.galgel, 187.facerec, and 191.fma3d in cpu2000.

For 200.sixtrack and 301.apsi in cpu2000 for some reason I had to use

PORTABILITY = -std=legacy

[Bug libgomp/91473] Test case libgomp.fortran/appendix-a/a.28.5.f90 is invalid

2019-08-17 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91473

Thomas Koenig  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2019-08-17
 CC||jakub at gcc dot gnu.org
  Component|fortran |libgomp
   Target Milestone|--- |10.0
Summary|[10 regression] test case   |Test case
   |libgomp.fortran/appendix-a/ |libgomp.fortran/appendix-a/
   |a.28.5.f90 fails starting   |a.28.5.f90 is invalid
   |with r274551|
 Ever confirmed|0   |1

--- Comment #7 from Thomas Koenig  ---
The test case is "fixed".  Removed regression marker. Somebody who
knows more about OMP than I do can figure out what this test is
actually testing, and how to make it valid (if that is possible).