public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "shb at gatech dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/107227] New: Compiler bug in private allocatable array in OpenACC compute statement Date: Wed, 12 Oct 2022 02:29:04 +0000 [thread overview] Message-ID: <bug-107227-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107227 Bug ID: 107227 Summary: Compiler bug in private allocatable array in OpenACC compute statement Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: shb at gatech dot edu CC: jakub at gcc dot gnu.org Target Milestone: --- The program below does not compile (nor does any variant of it involving allocatable statements that I can think of). ``` program main integer :: i real, allocatable :: arr(:) allocate(arr(10)) !$acc parallel loop private(arr) do i=1,10 arr=1.0 end do end ``` The error is ``` !$acc parallel loop private(arr) | ^ internal compiler error: in expand_oacc_for, at omp-expand.cc:7660 ``` A version of this suggested by Mat Colgrove also does not work: ``` program main integer :: i real, allocatable :: arr(:) allocate(arr(10)) !$acc parallel loop private(arr(1:10) do i=1,10 arr=1.0 end do end ``` with error ``` 5 | !$acc parallel loop private(arr(1:10)) | 1 Error: Syntax error in OpenMP variable list at (1) ``` These appear to be ICE compiler bugs as they are permitted by quite old OpenaCC standards (and are seemingly typical use cases of OpenACC in Fortran). nvhpc compilers work fine for this. The compile statement is `gfortran -foffload-options=-march=gfx90a -fopenacc test.f90` with offloading onto an AMD MI210.
next reply other threads:[~2022-10-12 2:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-12 2:29 shb at gatech dot edu [this message] 2022-10-12 7:26 ` [Bug libgomp/107227] " tschwinge at gcc dot gnu.org 2022-10-12 8:03 ` tschwinge at gcc dot gnu.org 2022-10-12 12:32 ` shb at gatech dot edu
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-107227-4@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).