public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <andrew_stubbs@mentor.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: DSE and maskstore trouble
Date: Tue, 03 Jul 2018 11:38:00 -0000	[thread overview]
Message-ID: <1c2e2b84-694f-770a-8db5-2e77a7123cda@mentor.com> (raw)
In-Reply-To: <CAFiYyc0htULzK3W-RVdALC3f+jFtTpqq-k85PbMavYOCyHg6og@mail.gmail.com>

On 03/07/18 12:30, Richard Biener wrote:
>> Hmm, so they're safe, but may prevent the optimization of nearby variables?
> 
> Yes, they prevent earlier stores into lanes that are "really" written
> to to be DSEd.

Right, but I have unrelated variables allocated to the stack within the 
"shadow" of the masked vector. I didn't ask it to do that, it just does, 
so I presume this is an expect feature of masked vectors with a known mask.

Surely this prevents valid optimizations on those variables?

Andrew

  reply	other threads:[~2018-07-03 11:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03  9:59 Andrew Stubbs
2018-07-03 10:16 ` Richard Biener
2018-07-03 10:33   ` Andrew Stubbs
2018-07-03 10:57     ` Andrew Stubbs
2018-07-03 11:02       ` Richard Biener
2018-07-03 11:06         ` Andrew Stubbs
2018-07-03 11:31           ` Richard Biener
2018-07-03 11:38             ` Andrew Stubbs [this message]
2018-07-03 11:46               ` Richard Biener
2018-07-03 11:57                 ` Andrew Stubbs
2018-07-03 12:21                   ` Richard Biener
2018-07-03 12:46                     ` Andrew Stubbs
2018-07-03 13:52                       ` Richard Biener
2018-07-03 15:19                         ` Andrew Stubbs
2018-07-03 16:45                           ` Richard Biener

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=1c2e2b84-694f-770a-8db5-2e77a7123cda@mentor.com \
    --to=andrew_stubbs@mentor.com \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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).