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/96244] Redudant mask load generated
Date: Mon, 20 Jul 2020 06:56:27 +0000	[thread overview]
Message-ID: <bug-96244-4-1xQhBALenh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96244-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2020-07-20
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |missed-optimization

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
So one thing to note here is that a masked load of a by-value parameter decl
doesn't make much sense since a load from it cannot trap (unless there's
out-of-bound accesses - which I'm not sure we may simply disregard here).

if-conversion sees

VIEW_CONVERT_EXPR<int[8]>(d)[i_16]

and indeed considers it

iftmp.0_11 = VIEW_CONVERT_EXPR<int[8]>(c)[i_17];
tree could trap...

  <bb 3> [local count: 954449105]:
  # RANGE [0, 8] NONZERO 15
  # i_17 = PHI <0(2), i_13(8)>
  # ivtmp_6 = PHI <8(2), ivtmp_4(8)>
  _1 = VIEW_CONVERT_EXPR<int[8]>(a)[i_17];
  _2 = VIEW_CONVERT_EXPR<int[8]>(b)[i_17];

so range-info is one index too pessimistic here.  So IMHO it's not about
"redundant" masked loads, it's about the fact that we end up with loads
at all here.  If c and d would not be register arguments we would have to
perform loads and if they might trap we could not elide the masked load.

  reply	other threads:[~2020-07-20  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  3:38 [Bug tree-optimization/96244] New: " crazylht at gmail dot com
2020-07-20  6:56 ` rguenth at gcc dot gnu.org [this message]
2020-07-20  7:33 ` [Bug tree-optimization/96244] " crazylht at gmail dot com
2021-03-24  8:34 ` crazylht at gmail dot com

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-96244-4-1xQhBALenh@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).