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/109880] New: [14 regression] gcc.target/powerpc/fold-vec-extract-int.p8.c fails after r14-916-g9417b30499ce09
Date: Tue, 16 May 2023 22:11:00 +0000	[thread overview]
Message-ID: <bug-109880-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109880
           Summary: [14 regression]
                    gcc.target/powerpc/fold-vec-extract-int.p8.c fails
                    after r14-916-g9417b30499ce09
           Product: gcc
           Version: 14.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:9417b30499ce09996b4f1b4e2ce75a2853865ed4, r14-916-g9417b30499ce09
make  -k check-gcc
RUNTESTFLAGS="powerpc.exp=gcc.target/powerpc/fold-vec-extract-int.p8.c"
FAIL: gcc.target/powerpc/fold-vec-extract-int.p8.c scan-assembler-times
\\mrldicl\\M 7
# of expected passes            11
# of unexpected failures        1


The test case may just need updating.  The ones that count assembler
instructions can be fragile.


commit 9417b30499ce09996b4f1b4e2ce75a2853865ed4 (HEAD, refs/bisect/bad)
Author: <E2><80><9C>Ajit Kumar Agarwal<E2><80><9D> <aagarwa1@linux.ibm.com>
Date:   Tue May 16 10:47:15 2023 -0500

    rs6000: Enable REE pass by default

             reply	other threads:[~2023-05-16 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 22:11 seurer at gcc dot gnu.org [this message]
2023-05-17  1:18 ` [Bug testsuite/109880] " bergner at gcc dot gnu.org
2023-05-18 10:17 ` aagarwa at gcc dot gnu.org
2023-06-13  8:37 ` cvs-commit at gcc dot gnu.org
2023-07-15  6:03 ` pinskia at gcc dot gnu.org
2023-07-17  2:25 ` 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-109880-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).