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/100905] New: [OpenMP] ICE in convert_nonlocal_omp_clauses, at tree-nested.c:1514 with 'omp loop' in Fortran internal procedure Date: Fri, 04 Jun 2021 16:50:11 +0000 [thread overview] Message-ID: <bug-100905-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100905 Bug ID: 100905 Summary: [OpenMP] ICE in convert_nonlocal_omp_clauses, at tree-nested.c:1514 with 'omp loop' in Fortran internal procedure Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code 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 50928 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50928&action=edit foo.f90 Long version of the testcase: https://github.com/SOLLVE/sollve_vv/blob/master/tests/5.0/loop/test_loop_order_concurrent.F90 The following testcase works when the '!$omp loop' is in the main program or a separate (module) procedure – but it ICEs when it is an internal procedure: # gfortran foo.f90 -fopenmp internal compiler error: in convert_nonlocal_omp_clauses, at tree-nested.c:1514 0x7118d7 convert_nonlocal_omp_clauses ../../repos/gcc-trunk-commit/gcc/tree-nested.c:1514 0xf455ed convert_nonlocal_reference_stmt ../../repos/gcc-trunk-commit/gcc/tree-nested.c:1708
next reply other threads:[~2021-06-04 16:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 16:50 burnus at gcc dot gnu.org [this message] 2021-06-04 17:03 ` [Bug middle-end/100905] " burnus at gcc dot gnu.org 2021-06-04 18:55 ` cvs-commit at gcc dot gnu.org 2021-06-04 20:24 ` burnus at gcc dot gnu.org 2021-09-17 6:47 ` pinskia 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-100905-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).