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/111850] [14 regression] gcc.target/powerpc/fold-vec-extract-char.p7.c fails after r14-4664-g04c9cf5c786b94
Date: Tue, 17 Oct 2023 21:28:25 +0000 [thread overview]
Message-ID: <bug-111850-4-3M7ueqS5wE@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
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Keywords| |testsuite-fail
Last reconfirmed| |2023-10-17
Target Milestone|--- |14.0
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It looks like the new pass is creating better code.
Before:
< addi 10,5,-48
< add 5,10,1
18c15,17
< lbz 3,32(5)
After:
> add 5,5,1
> lbz 3,-16(5)
Removing the addi by doing a quick reassociation .
next prev parent reply other threads:[~2023-10-17 21:28 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 ` pinskia at gcc dot gnu.org [this message]
2023-10-18 13:34 ` [Bug testsuite/111850] [14 regression] gcc.target/powerpc/fold-vec-extract-char.p7.c fails after r14-4664-g04c9cf5c786b94 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
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-3M7ueqS5wE@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).