public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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: Wed, 20 Jul 2022 08:25:20 +0000 [thread overview]
Message-ID: <bug-106365-4-CQFJjO2bGk@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
What's the semantic of .LEN_STORE? I can't find documentation for this :/
There's docs for the len_store optab but how 'mask' and 'bias' relate to its
operands isn't documented anywhere. If the cited .LEN_STORE is a full store
then sure - folding to a plain MEM = value; is preferred. Otherwise I wouldn't
split it up. Handling of partial stores in VN is possible, the "easiest" way
is probably via vn_reference_lookup_3 and its support for partial defs
(for constant masks a store may then be composed of multiple partial defs
and "masked" parts that are required will be taken from earlier stores).
Maybe handling of all partial store IFNs can be commonized somehow.
Alias analysis in general (ref_maybe_used_by_stmt_p, call_may_clobber_ref_p,
stmt_kills_ref_p) also miss handling of them - possibly some more general
helpers can facilitate that.
next prev parent reply other threads:[~2022-07-20 8:25 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 [this message]
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
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-CQFJjO2bGk@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).