public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/110725] [13/14 Regression] internal compiler error: in expand_expr_real_1, at expr.cc:10897
Date: Wed, 19 Jul 2023 17:44:48 +0000 [thread overview]
Message-ID: <bug-110725-4-AKFc4Bnc74@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110725-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110725
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |14.0
Known to work| |12.2.0
--- Comment #4 from kargl at gcc dot gnu.org ---
(In reply to Richard Biener from comment #3)
> That would make it accepts-invalid then?
I'm not an expert with OpenMP, so cannot make a decision here.
Note, the original code compiles with 12.2.0. I don't have
13.x installed for testing.
While reducing the code to something much smaller, I notice the
idiom of
!$omp target
!$omp teams
!$omp distribute parallel do simd
DO 75 I=1,M
<Fortran code here>
75 CONTINUE
!$omp end teams
!$omp end target
everywhere except for the one occurrence in the reduce code of
!$omp target
!$omp teams
!$omp distribute parallel do simd
DO 75 I=1,M
U(I+1,N+1) = U(I+1,1)
V(I,1) = V(I,N+1)
75 CONTINUE
!$omp end teams
U(1,N+1) = U(M+1,1) <-- This seems out-of-place when compared
V(M+1,1) = V(1,N+1) <-- to all other code.
!$omp end target
END SUBROUTINE
If I move the '!$omp end teams' down two lines, the code compiles. If I remove
the two lines of Fortran code, the code compiles.
next prev parent reply other threads:[~2023-07-19 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 17:22 [Bug fortran/110725] New: " tonycurtis32 at gmail dot com
2023-07-18 17:56 ` [Bug fortran/110725] [13/14 Regression] " anlauf at gcc dot gnu.org
2023-07-18 18:55 ` [Bug fortran/110725] [13/14 Regression,openmp] " kargl at gcc dot gnu.org
2023-07-19 6:47 ` [Bug fortran/110725] [13/14 Regression] " rguenth at gcc dot gnu.org
2023-07-19 17:44 ` kargl at gcc dot gnu.org [this message]
2023-07-24 15:04 ` jakub at gcc dot gnu.org
2023-07-24 20:58 ` cvs-commit at gcc dot gnu.org
2023-07-25 13:45 ` cvs-commit at gcc dot gnu.org
2023-07-27 9:27 ` rguenth at gcc dot gnu.org
2023-07-27 16:17 ` cvs-commit at gcc dot gnu.org
2024-03-04 4:54 ` law at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-110725-4-AKFc4Bnc74@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).