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 tree-optimization/106365] Miss to handle ifn .LEN_STORE in FRE
Date: Thu, 21 Jul 2022 11:06:53 +0000 [thread overview]
Message-ID: <bug-106365-4-D4TROC2Wvv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106365-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106365
--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:bd9837bc3ca1344c32aef7ba9f8fa1785063132e
commit r13-1777-gbd9837bc3ca1344c32aef7ba9f8fa1785063132e
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jul 20 12:28:26 2022 +0200
Teach VN about masked/len stores
The following teaches VN to handle reads from .MASK_STORE and
.LEN_STORE. For this push_partial_def is extended first for
convenience so we don't have to handle the full def case in the
caller (possibly other paths can be simplified then). Also
the partial definition stored value can have an offset applied
so we don't have to build a fake RHS when we register the pieces
of an existing store.
PR tree-optimization/106365
* tree-ssa-sccvn.cc (pd_data::rhs_off): New field determining
the offset to start encoding of RHS from.
(vn_walk_cb_data::vn_walk_cb_data): Initialize it.
(vn_walk_cb_data::push_partial_def): Allow the first partial
definition to be fully providing the def. Offset RHS
before encoding if requested.
(vn_reference_lookup_3): Initialize def_rhs everywhere.
Add support for .MASK_STORE and .LEN_STORE (partial) definitions.
* gcc.target/i386/vec-maskstore-vn.c: New testcase.
next prev parent reply other threads:[~2022-07-21 11:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 5:25 [Bug tree-optimization/106365] New: " linkw at gcc dot gnu.org
2022-07-20 7:35 ` [Bug tree-optimization/106365] " linkw at gcc dot gnu.org
2022-07-20 8:25 ` rguenth at gcc dot gnu.org
2022-07-20 8:53 ` linkw at gcc dot gnu.org
2022-07-20 9:01 ` rguenth at gcc dot gnu.org
2022-07-20 9:07 ` rguenth at gcc dot gnu.org
2022-07-20 9:11 ` linkw at gcc dot gnu.org
2022-07-20 10:34 ` rguenth at gcc dot gnu.org
2022-07-20 12:07 ` rguenth at gcc dot gnu.org
2022-07-21 7:26 ` rguenth at gcc dot gnu.org
2022-07-21 7:30 ` linkw at gcc dot gnu.org
2022-07-21 7:31 ` rguenth at gcc dot gnu.org
2022-07-21 7:37 ` linkw at gcc dot gnu.org
2022-07-21 7:39 ` rguenth at gcc dot gnu.org
2022-07-21 7:57 ` linkw at gcc dot gnu.org
2022-07-21 11:06 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-21 11:24 ` 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-106365-4-D4TROC2Wvv@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).