public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107236] New: [OpenMP] ICE for reverse offload: in expand_GOMP_TARGET_REV, at internal-fn.cc:376 Date: Wed, 12 Oct 2022 13:35:56 +0000 [thread overview] Message-ID: <bug-107236-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107236 Bug ID: 107236 Summary: [OpenMP] ICE for reverse offload: in expand_GOMP_TARGET_REV, at internal-fn.cc:376 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, openmp Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- Created attachment 53696 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53696&action=edit Testcase - compile as: gfortran -fopenmp test.f90 This only shows up if ENABLE_OFFLOADING is true during the GCC build. The attached testcase fails with: rev-test-ice.f90:5:33: internal compiler error: in expand_GOMP_TARGET_REV, at internal-fn.cc:376 5 | !$omp target device(ancestor:1) | ^ 0x791309 expand_GOMP_TARGET_REV /net/build1-fossa-cs/scratch/tburnus/fsf.mainline.x86_64-linux-gnu-amdgcn/src/gcc-mainline/gcc/internal-fn.cc:376 0xb2c147 expand_call_stmt
next reply other threads:[~2022-10-12 13:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-12 13:35 burnus at gcc dot gnu.org [this message] 2022-10-12 13:47 ` [Bug middle-end/107236] " burnus at gcc dot gnu.org 2022-10-24 13:20 ` cvs-commit at gcc dot gnu.org 2022-10-24 13:25 ` burnus 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-107236-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).