public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102621] ICE in convert_nonlocal_reference_op, at tree-nested.c:1166 since r12-1108-g9a5de4d5af1c10a8
Date: Thu, 20 Jan 2022 09:23:01 +0000 [thread overview]
Message-ID: <bug-102621-4-h0Sn5mlrrc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102621-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102621
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|12.0 |---
Summary|[12 Regression] ICE in |ICE in
|convert_nonlocal_reference_ |convert_nonlocal_reference_
|op, at tree-nested.c:1166 |op, at tree-nested.c:1166
|since |since
|r12-1108-g9a5de4d5af1c10a8 |r12-1108-g9a5de4d5af1c10a8
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's not clear that only Fortran is affected but GCC 11 rejected the code with
t.f90:3:15:
3 | !$omp task affinity (iterator(j=1:8) : a(j))
| 1
Error: Failed to match clause at (1)
t.f90:4:17:
4 | !$omp end task
| 1
Error: Unexpected !$OMP END TASK statement at (1)
so it's not a regression.
next prev parent reply other threads:[~2022-01-20 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 18:36 [Bug fortran/102621] New: [12 Regression] ICE in convert_nonlocal_reference_op, at tree-nested.c:1166 gscfq@t-online.de
2021-10-06 8:41 ` [Bug fortran/102621] " rguenth at gcc dot gnu.org
2021-10-11 8:28 ` [Bug fortran/102621] [12 Regression] ICE in convert_nonlocal_reference_op, at tree-nested.c:1166 since r12-1108-g9a5de4d5af1c10a8 marxin at gcc dot gnu.org
2022-01-20 9:23 ` rguenth at gcc dot gnu.org [this message]
2022-01-20 16:01 ` [Bug fortran/102621] " sandra at gcc dot gnu.org
2022-01-20 21:30 ` cvs-commit 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-102621-4-h0Sn5mlrrc@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: link
Be 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).