public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <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 07:33:16 +0000	[thread overview]
Message-ID: <bug-96244-4-aiJj7D2VY9@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

--- Comment #2 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> 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.

compared to masked load, load seems to be be more probably eliminated by
backend for this situation.

  parent reply	other threads:[~2020-07-20  7:33 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 ` [Bug tree-optimization/96244] " rguenth at gcc dot gnu.org
2020-07-20  7:33 ` crazylht at gmail dot com [this message]
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-aiJj7D2VY9@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).