public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/102310] [11/12 Regression] ICE in visit_ref_for_mod_analysis with OpenACC
Date: Tue, 14 Sep 2021 07:35:47 +0000 [thread overview]
Message-ID: <bug-102310-4-FNfxawl0Do@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102310-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102310
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |openacc
CC| |jules at gcc dot gnu.org
Target|gcn |
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Both ICEs confirmed. Does need '-fopenacc' to reproduce, but doesn't need an
actual GCC offloading configuration; ICEs in host compilation.
Julian, please have a look at the test case: should GCC be able to handle that
one fine, or is "something" missing in GCC/OpenACC; ICE of course is not the
correct answer in any case. ;-)
Also, note that the "w/o any optimization level" ICE looks like what I recently
also ran into (still un-fixed), when working on reference data type things --
which I suppose is relevant here, as these are Fortran dummy arguments to a
'SUBROUTINE'.
next prev parent reply other threads:[~2021-09-14 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 17:06 [Bug middle-end/102310] New: " ygribov at gcc dot gnu.org
2021-09-14 6:54 ` [Bug ipa/102310] [11/12 Regression] " rguenth at gcc dot gnu.org
2021-09-14 7:19 ` marxin at gcc dot gnu.org
2021-09-14 7:35 ` tschwinge at gcc dot gnu.org [this message]
2021-09-14 8:48 ` tetra2005 at gmail dot com
2021-10-07 15:54 ` hubicka at gcc dot gnu.org
2021-10-08 9:07 ` jamborm at gcc dot gnu.org
2022-04-21 7:50 ` rguenth at gcc dot gnu.org
2022-09-23 15:23 ` [Bug ipa/102310] [11/12/13 " tschwinge at gcc dot gnu.org
2023-05-29 10:05 ` [Bug ipa/102310] [11/12/13/14 " jakub at gcc dot gnu.org
2024-04-30 13:04 ` [Bug ipa/102310] [11/12 " jamborm 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-102310-4-FNfxawl0Do@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).