public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/111850] [14 regression] gcc.target/powerpc/fold-vec-extract-char.p7.c fails after r14-4664-g04c9cf5c786b94
Date: Thu, 18 Jan 2024 06:01:41 +0000	[thread overview]
Message-ID: <bug-111850-4-QD6702xO9h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111850-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:f4156fbf7d6d641f8aade8028e87cf302350c3c0

commit r14-8201-gf4156fbf7d6d641f8aade8028e87cf302350c3c0
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Thu Jan 18 00:00:52 2024 -0600

    testsuite, rs6000: Adjust fold-vec-extract-char.p7.c [PR111850]

    As PR101169 comment #c4 shows, previsouly the addi count
    update on fold-vec-extract-char.p7.c covered a sub-optimal
    code gen issue.  On trunk, pass fold-mem-offsets helps to
    recover the best code sequence, so this patch is to
    revert the count back to the original which matches the
    optimal addi count.

            PR testsuite/111850

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/fold-vec-extract-char.p7.c: Update the
            checking count of addi to 6.

  parent reply	other threads:[~2024-01-18  6:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 19:40 [Bug testsuite/111850] New: [14 regression] seurer at gcc dot gnu.org
2023-10-17 21:28 ` [Bug testsuite/111850] [14 regression] gcc.target/powerpc/fold-vec-extract-char.p7.c fails after r14-4664-g04c9cf5c786b94 pinskia at gcc dot gnu.org
2023-10-18 13:34 ` seurer at gcc dot gnu.org
2023-10-19  6:13 ` linkw at gcc dot gnu.org
2024-01-15 13:56 ` rguenth at gcc dot gnu.org
2024-01-16  3:01 ` linkw at gcc dot gnu.org
2024-01-18  6:01 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-18  6:29 ` 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-111850-4-QD6702xO9h@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).