public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/114373] New: BLOCK construct not correctly analyzed with -fopenmp
@ 2024-03-18 6:21 Jens-Olaf.Beismann at emea dot nec.com
2024-03-18 17:28 ` [Bug fortran/114373] [12/13 Regression] " anlauf at gcc dot gnu.org
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Jens-Olaf.Beismann at emea dot nec.com @ 2024-03-18 6:21 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114373
Bug ID: 114373
Summary: BLOCK construct not correctly analyzed with -fopenmp
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: Jens-Olaf.Beismann at emea dot nec.com
Target Milestone: ---
Created attachment 57721
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57721&action=edit
Test code
Following error messages are erroneously issued when compiling with -fopenmp:
% gfortran -c -fopenmp tfx.f90
tfx.f90:17:58:
17 | goto_9999 = .TRUE. ; EXIT store_field_critical_0
| 1
Error: EXIT statement at (1) is not within construct 'store_field_critical_0'
tfx.f90:27:60:
27 | goto_9999 = .TRUE. ; EXIT store_field_critical_0
| 1
Error: EXIT statement at (1) is not within construct 'store_field_critical_0'
tfx.f90:31:34:
31 | END BLOCK store_field_critical_0
| 1
Error: Syntax error in END BLOCK statement at (1)
tfx.f90:32:34:
32 | !$OMP END CRITICAL (store_field_0)
| 1
Error: Unexpected !$OMP END CRITICAL statement at (1)
tfx.f90:37:3:
37 | END SUBROUTINE store_field
| 1
Error: Expecting END BLOCK statement at (1)
f951: Error: Unexpected end of file in 'tfx.f90'
Compilation without OpenMP support or with compiler versions 11.2.0 or earlier
works as expected. Test code and compiler version information attached.
Thank you and best regards,
Jens-Olaf
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/114373] [12/13 Regression] BLOCK construct not correctly analyzed with -fopenmp
2024-03-18 6:21 [Bug fortran/114373] New: BLOCK construct not correctly analyzed with -fopenmp Jens-Olaf.Beismann at emea dot nec.com
@ 2024-03-18 17:28 ` anlauf at gcc dot gnu.org
2024-04-14 5:21 ` pinskia at gcc dot gnu.org
2024-05-21 9:19 ` jakub at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: anlauf at gcc dot gnu.org @ 2024-03-18 17:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114373
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|BLOCK construct not |[12/13 Regression] BLOCK
|correctly analyzed with |construct not correctly
|-fopenmp |analyzed with -fopenmp
Known to work| |10.5.0, 11.4.1, 14.0, 9.5.0
Last reconfirmed| |2024-03-18
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Priority|P3 |P4
Known to fail| |12.3.1, 13.2.1
CC| |anlauf at gcc dot gnu.org
--- Comment #1 from anlauf at gcc dot gnu.org ---
Appears to be fixed on 14-mainline.
Can we identify the fix for it?
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/114373] [12/13 Regression] BLOCK construct not correctly analyzed with -fopenmp
2024-03-18 6:21 [Bug fortran/114373] New: BLOCK construct not correctly analyzed with -fopenmp Jens-Olaf.Beismann at emea dot nec.com
2024-03-18 17:28 ` [Bug fortran/114373] [12/13 Regression] " anlauf at gcc dot gnu.org
@ 2024-04-14 5:21 ` pinskia at gcc dot gnu.org
2024-05-21 9:19 ` jakub at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-04-14 5:21 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114373
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |13.3
Keywords| |needs-bisection
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/114373] [12/13 Regression] BLOCK construct not correctly analyzed with -fopenmp
2024-03-18 6:21 [Bug fortran/114373] New: BLOCK construct not correctly analyzed with -fopenmp Jens-Olaf.Beismann at emea dot nec.com
2024-03-18 17:28 ` [Bug fortran/114373] [12/13 Regression] " anlauf at gcc dot gnu.org
2024-04-14 5:21 ` pinskia at gcc dot gnu.org
@ 2024-05-21 9:19 ` jakub at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: jakub at gcc dot gnu.org @ 2024-05-21 9:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114373
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|13.3 |13.4
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 13.3 is being released, retargeting bugs to GCC 13.4.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-05-21 9:19 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-18 6:21 [Bug fortran/114373] New: BLOCK construct not correctly analyzed with -fopenmp Jens-Olaf.Beismann at emea dot nec.com
2024-03-18 17:28 ` [Bug fortran/114373] [12/13 Regression] " anlauf at gcc dot gnu.org
2024-04-14 5:21 ` pinskia at gcc dot gnu.org
2024-05-21 9:19 ` jakub at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).