public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/105267] New: [12 regression] gcc.target/powerpc/pr56605.c fails after r12-8128-g6b7cc7294770ec
Date: Wed, 13 Apr 2022 20:44:59 +0000	[thread overview]
Message-ID: <bug-105267-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105267
           Summary: [12 regression] gcc.target/powerpc/pr56605.c fails
                    after r12-8128-g6b7cc7294770ec
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:6b7cc7294770ecb57c0f3a116a27ce1aaff170b5, r12-8128-g6b7cc7294770ec
make  -k check-gcc RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/pr56605.c"
FAIL: gcc.target/powerpc/pr56605.c scan-rtl-dump-times combine "\\(compare:CC
\\((?:and|zero_extend):(?:[SD]I) \\((?:sub)?reg:[SD]I" 1
# of expected passes            1
# of unexpected failures        1

commit 6b7cc7294770ecb57c0f3a116a27ce1aaff170b5 (HEAD, refs/bisect/bad)
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Tue Apr 12 22:41:45 2022 -0300

    ppc: testsuite: PROMOTE_MODE fallout pr56605 [PR102146]

             reply	other threads:[~2022-04-13 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 20:44 seurer at gcc dot gnu.org [this message]
2022-04-14  6:31 ` [Bug testsuite/105267] " rguenth at gcc dot gnu.org
2022-04-20  2:14 ` linkw at gcc dot gnu.org
2022-04-20  2:15 ` linkw at gcc dot gnu.org
2022-04-23 15:00 ` aoliva at gcc dot gnu.org
2022-05-06  8:33 ` [Bug testsuite/105267] [12/13 " jakub at gcc dot gnu.org
2022-07-26 11:45 ` rguenth at gcc dot gnu.org
2023-04-18  1:59 ` [Bug testsuite/105267] [12/13/14 " linkw 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-105267-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).