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,openmp] internal compiler error: in expand_expr_real_1, at expr.cc:10897 Date: Tue, 18 Jul 2023 18:55:03 +0000 [thread overview] Message-ID: <bug-110725-4-CFp7aM8gqv@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 ---------------------------------------------------------------------------- Summary|[13/14 Regression] internal |[13/14 Regression,openmp] |compiler error: in |internal compiler error: in |expand_expr_real_1, at |expand_expr_real_1, at |expr.cc:10897 |expr.cc:10897 CC| |kargl at gcc dot gnu.org --- Comment #2 from kargl at gcc dot gnu.org --- Reduced testcase. The '!$omp end teams' line in subroutine initial appears to be out-of-place. module swim_mod INTEGER, PARAMETER :: N1=7702, N2=7702 DOUBLE PRECISION, ALLOCATABLE, DIMENSION(:,:) :: U, V INTEGER :: M, N, MP1, NP1 !$omp declare target(U, V) !$omp declare target(M,N,MP1,NP1) CONTAINS SUBROUTINE ALLOC IMPLICIT NONE !$omp target update to(M,N,MP1,NP1) !$omp& ALLOCATE(U(NP1,MP1), V(NP1,MP1)) END SUBROUTINE SUBROUTINE INITAL INTEGER I !$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) V(M+1,1) = V(1,N+1) !$omp end target END SUBROUTINE end module swim_mod
next prev parent reply other threads:[~2023-07-18 18:55 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 ` kargl at gcc dot gnu.org [this message] 2023-07-19 6:47 ` rguenth at gcc dot gnu.org 2023-07-19 17:44 ` kargl at gcc dot gnu.org 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-CFp7aM8gqv@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: linkBe 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).