public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "luoxhu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98827] [11 regression] gcc.target/powerpc/vsx-builtin-7.c assembler counts off after r11-6857
Date: Wed, 27 Jan 2021 01:45:17 +0000	[thread overview]
Message-ID: <bug-98827-4-euHG9i29oG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98827-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from luoxhu at gcc dot gnu.org ---
I know it now, the r11-6858 did some changes the P8 code generation, so the
latest failure also changes.

https://gcc.gnu.org/pipermail/gcc-testresults/2021-January/651154.html

current failures are:

FAIL: gcc.dg/vect/vect-outer-call-1.c scan-tree-dump vect "OUTER LOOP
VECTORIZED"
FAIL: gcc.dg/vect/vect-strided-a-u8-i2-gap.c -flto -ffat-lto-objects 
scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-strided-a-u8-i2-gap.c scan-tree-dump-times vect
"vectorized 1 loops" 1
FAIL: gcc.target/powerpc/20050603-3.c scan-assembler-not \\\\mrldic
FAIL: gcc.target/powerpc/rlwimi-2.c scan-assembler-times (?n)^\\\\s+[a-z] 20217
FAIL: gcc.target/powerpc/vsx-builtin-7.c scan-assembler-times xxpermdi 11
XPASS: gcc.target/powerpc/ppc-fortran/ieee128-math.f90   -O  (test for excess
errors)

only xxpermdi need be updated to 4.

  parent reply	other threads:[~2021-01-27  1:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 21:08 [Bug target/98827] New: " seurer at gcc dot gnu.org
2021-01-26  1:40 ` [Bug target/98827] " luoxhu at gcc dot gnu.org
2021-01-26  8:08 ` rguenth at gcc dot gnu.org
2021-01-26 15:14 ` seurer at gcc dot gnu.org
2021-01-27  1:45 ` luoxhu at gcc dot gnu.org [this message]
2021-01-28  3:35 ` cvs-commit at gcc dot gnu.org
2021-02-26 12:34 ` 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-98827-4-euHG9i29oG@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).