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/106534] New: [13 Regression][gcn] ICE 'verify_ssa failed' / 'error: definition in block 18 does not dominate use in block 19' during libgfortran bootstrap
Date: Fri, 05 Aug 2022 09:02:01 +0000	[thread overview]
Message-ID: <bug-106534-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106534
           Summary: [13 Regression][gcn] ICE 'verify_ssa failed' / 'error:
                    definition in block 18 does not dominate use in block
                    19' during libgfortran bootstrap
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: build, 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
                CC: ams at gcc dot gnu.org
  Target Milestone: ---
            Target: amdgcn-amdhsa

Build of amdgcn-amdhsa (as offloading compiler for/on x86_64-gnu-linux) fails
to build as follows. It did bootstrap successfully a few days back (like Aug 2
or 3):


src/gcc-mainline/libgfortran/io/unit.c: In function 'get_gfc_unit':
src/gcc-mainline/libgfortran/io/unit.c:326:1: error: definition in block 18
does not dominate use in block 19
  326 | get_gfc_unit (int n, int do_create)
      | ^~~~~~~~~~~~
for SSA_NAME: p_47 in statement:
p_30 = PHI <p_47(19), p_47(38)>
PHI argument
p_47
for PHI node
p_30 = PHI <p_47(19), p_47(38)>
during GIMPLE pass: phiopt
/scratch/ci-cs/amdtest/upstream-offload/src/gcc-mainline/libgfortran/io/unit.c:326:1:
internal compiler error: verify_ssa failed

             reply	other threads:[~2022-08-05  9:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  9:02 burnus at gcc dot gnu.org [this message]
2022-08-05  9:11 ` [Bug middle-end/106534] " rguenth at gcc dot gnu.org
2022-08-05 10:23 ` burnus at gcc dot gnu.org
2022-08-05 10:49 ` tnfchris at gcc dot gnu.org
2022-08-05 10:54 ` burnus at gcc dot gnu.org
2022-08-05 10:56 ` rguenther at suse dot de
2022-08-05 11:03 ` tnfchris at gcc dot gnu.org
2022-08-05 11:06 ` burnus at gcc dot gnu.org
2022-08-05 11:17 ` tnfchris at gcc dot gnu.org
2022-08-05 11:24 ` tnfchris at gcc dot gnu.org
2022-08-05 13:54 ` cvs-commit at gcc dot gnu.org
2022-08-05 13:56 ` tnfchris 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-106534-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: 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).