public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113502] New: gcc.target/aarch64/vect-early-break-cbranch.c testcase is too sensitive
Date: Fri, 19 Jan 2024 11:07:35 +0000	[thread overview]
Message-ID: <bug-113502-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113502
           Summary: gcc.target/aarch64/vect-early-break-cbranch.c testcase
                    is too sensitive
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: testsuite-fail
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64

Currently vect-early-break-cbranch.c fails.

For the failure we have:
```
FAIL: gcc.target/aarch64/vect-early-break-cbranch.c check-function-bodies f1
body: .*\tcmge  v[0-9]+.4s, v[0-9]+.4s, #0
\tumaxp v[0-9]+.4s, v[0-9]+.4s, v[0-9]+.4s
\tfmov  x[0-9]+, d[0-9]+
\tcbnz  x[0-9]+, \.L[0-9]+
.*
...
        cmge    v31.4s, v31.4s, #0
        umaxp   v31.4s, v31.4s, v31.4s
        fmov    x3, d31
        cbz     x3, .L11
```

As you can see it does not match as it is trying to match cbnz but cbz is
emitted.

             reply	other threads:[~2024-01-19 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 11:07 pinskia at gcc dot gnu.org [this message]
2024-01-19 11:12 ` [Bug testsuite/113502] gcc.target/aarch64/vect-early-break-cbranch.c and gcc.target/aarch64/sve/vect-early-break-cbranch.c testcase are " pinskia at gcc dot gnu.org
2024-01-31 14:53 ` cvs-commit at gcc dot gnu.org
2024-01-31 14:55 ` 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-113502-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).