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 fortran/106730] New: [OpenMP] ICE in install_var_field, at omp-low.cc:797 Date: Wed, 24 Aug 2022 06:45:06 +0000 [thread overview] Message-ID: <bug-106730-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106730 Bug ID: 106730 Summary: [OpenMP] ICE in install_var_field, at omp-low.cc:797 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, openmp Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- Created attachment 53499 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53499&action=edit Slightly modified and de-module-used testcase; run as 'gfortran -fopenmp test.f90' Found via https://github.com/SOLLVE/sollve_vv/blob/master/tests/5.0/target/test_target_mapping_before_alloc.F90 Testcase fails since at least GCC 9. $ gfortran -fopenmp test.f90 during GIMPLE pass: omplower test.f90:25:41: 25 | !$omp& test_struct) map(tofrom: errors) | ^ internal compiler error: in install_var_field, at omp-low.cc:797 0x742f21 install_var_field ../../repos/gcc-trunk-commit/gcc/omp-low.cc:797 0xe24f0c scan_sharing_clauses ../../repos/gcc-trunk-commit/gcc/omp-low.cc:1672 0xe26877 scan_omp_target ../../repos/gcc-trunk-commit/gcc/omp-low.cc:3100
next reply other threads:[~2022-08-24 6:45 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-24 6:45 burnus at gcc dot gnu.org [this message] 2022-08-24 6:55 ` [Bug fortran/106730] [OpenMP][valid since 5.0] ICE in install_var_field, at omp-low.cc:797 for 'map(alloc:var) map(to:var)' (more than once in map clause) 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-106730-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).