public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tetra2005 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/95550] [OpenACC] ICE in expand_oacc_for, at omp-expand.c:6075
Date: Tue, 28 Sep 2021 08:16:27 +0000	[thread overview]
Message-ID: <bug-95550-4-e6VELZ1fLu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95550-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95550

Yuri Gribov <tetra2005 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tetra2005 at gmail dot com

--- Comment #1 from Yuri Gribov <tetra2005 at gmail dot com> ---
Also fails on simpler code (on master and devel/omp/gcc-11 branches):

  $ gfortran -ffree-form -ffree-line-length-none -O2 -fopenacc -c kernel.f90
  kernel.f90:10:34:

   10 | !$ACC PARALLEL LOOP PRIVATE(GWORK)
      |                                  ^
  internal compiler error: in expand_oacc_for, at omp-expand.c:7529
  0x62c8b7 expand_oacc_for
          /home/y.gribov/src/gcc-omp/gcc/omp-expand.c:7529
  0x1605139 expand_omp_for
          /home/y.gribov/src/gcc-omp/gcc/omp-expand.c:8081
  0x1605afa expand_omp
          /home/y.gribov/src/gcc-omp/gcc/omp-expand.c:10302
  0x16053c5 expand_omp
          /home/y.gribov/src/gcc-omp/gcc/omp-expand.c:10288
  0x16079dd execute_expand_omp
          /home/y.gribov/src/gcc-omp/gcc/omp-expand.c:10536

  reply	other threads:[~2021-09-28  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05  9:58 [Bug middle-end/95550] New: " burnus at gcc dot gnu.org
2021-09-28  8:16 ` tetra2005 at gmail dot com [this message]
2021-09-28  8:56 ` [Bug middle-end/95550] " tetra2005 at gmail dot com
2022-10-12  7:26 ` tschwinge 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-95550-4-e6VELZ1fLu@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).