public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114234] New: [14 Regression] verify_ssa failure with early-break vectorisation
Date: Tue, 05 Mar 2024 10:46:32 +0000	[thread overview]
Message-ID: <bug-114234-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114234
           Summary: [14 Regression] verify_ssa failure with early-break
                    vectorisation
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rsandifo at gcc dot gnu.org
  Target Milestone: ---

The following test ICEs with -Ofast on aarch64:

void bar();
float
foo (float x)
{
  float a = 1;
  float b = x;
  long z = 200;
  for (;;)
    {
      float c = b - 1.0f;
      a *= c;
      z -= 1;
      if (z == 0)
        {
          bar ();
          break;
        }
      if (b <= 3.0f)
        break;
      b = c;
    }
  return a * b;
}

(reduced from wrf).  The ICE is:

foo.c:3:1: error: definition in block 15 does not dominate use in block 10
    3 | foo (float x)
      | ^~~
for SSA_NAME: stmp_a_9.10_103 in statement:
a_47 = PHI <stmp_a_9.10_103(10), stmp_a_9.10_103(15)>
PHI argument
stmp_a_9.10_103
for PHI node
a_47 = PHI <stmp_a_9.10_103(10), stmp_a_9.10_103(15)>
during GIMPLE pass: vect

             reply	other threads:[~2024-03-05 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 10:46 rsandifo at gcc dot gnu.org [this message]
2024-03-05 13:19 ` [Bug tree-optimization/114234] " dcb314 at hotmail dot com
2024-03-05 13:20 ` sjames at gcc dot gnu.org
2024-03-05 14:23 ` tnfchris at gcc dot gnu.org
2024-03-06 12:06 ` rguenth 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-114234-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).