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/107240] [13 Regression] FAIL: gcc.dg/vect/vect-bitfield-write-2.c since r13-3219-g25413fdb2ac249
Date: Thu, 20 Oct 2022 09:08:05 +0000 [thread overview]
Message-ID: <bug-107240-4-il5oYbaQS8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107240-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107240
--- Comment #9 from CVS 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:5d6e834ecf212e7fc6f585b154af224d2e38c749
commit r13-3396-g5d6e834ecf212e7fc6f585b154af224d2e38c749
Author: Kewen Lin <linkw@linux.ibm.com>
Date: Thu Oct 20 04:07:05 2022 -0500
vect: Simplify first for shifted value generation [PR107240]
As PR107240 shows, when both the value to be shifted and the
count used for shifting are constants, it can be simplified
to one constant value, and doesn't actually require to check
if the current target supports vector shift operations or not.
This patch uses a canonical way proposed by Richi to generate
the shifted value, if it can be simplified, the shift operation
would be gone, otherwise it's the same as before.
It can help to fix the failures of vect-bitfield-write-{2,3}.c
on Power.
PR tree-optimization/107240
2022-10-20 Richard Biener <rguenther@suse.de>
gcc/ChangeLog:
* tree-vect-patterns.cc (vect_recog_bit_insert_pattern): Attempt to
simplify shifted value first.
next prev parent reply other threads:[~2022-10-20 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 18:48 [Bug testsuite/107240] New: [13 regression] seurer at gcc dot gnu.org
2022-10-12 19:16 ` [Bug testsuite/107240] " bergner at gcc dot gnu.org
2022-10-13 6:49 ` [Bug testsuite/107240] [13 Regression] FAIL: gcc.dg/vect/vect-bitfield-write-2.c since r13-3219-g25413fdb2ac249 marxin at gcc dot gnu.org
2022-10-13 13:53 ` avieira at gcc dot gnu.org
2022-10-14 7:20 ` rguenth at gcc dot gnu.org
2022-10-14 16:44 ` segher at gcc dot gnu.org
2022-10-14 16:45 ` avieira at gcc dot gnu.org
2022-10-14 16:48 ` segher at gcc dot gnu.org
2022-10-17 4:04 ` linkw at gcc dot gnu.org
2022-10-17 6:21 ` linkw at gcc dot gnu.org
2022-10-18 5:56 ` linkw at gcc dot gnu.org
2022-10-18 8:06 ` rguenth at gcc dot gnu.org
2022-10-20 9:08 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-28 3:31 ` cvs-commit at gcc dot gnu.org
2022-10-28 3:44 ` 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-107240-4-il5oYbaQS8@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).