public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49093] [4.6/4.7 Regression] ICE in vect_enhance_data_refs_alignment() with volatile inside peeled loop
Date: Tue, 31 May 2011 08:54:00 -0000 [thread overview]
Message-ID: <bug-49093-4-pztBHC9V8V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49093-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49093
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> 2011-05-31 08:43:39 UTC ---
On Tue, 31 May 2011, irar at il dot ibm.com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49093
>
> --- Comment #5 from Ira Rosen <irar at il dot ibm.com> 2011-05-31 08:30:49 UTC ---
> (In reply to comment #4)
>
> > I think that's reasonable for 4.6. But we don't need to make
> > data-ref analysis fail just because of volatile references - we for
> > example can easily unroll a loop with volatile loads/stores.
> >
> > Of course this case seems to be special - how do we deal with
> > stmts with no uses during vectorization? Or do we assume
> > they don't happen because usually DCE gets rid of them?
>
> We ignore them. But this is under the assumption that they don't have memory
> accesses.
Ah, I see. Yes, I guess not vectorizing for volatiles is the way
to go then.
Richard.
next prev parent reply other threads:[~2011-05-31 8:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 19:08 [Bug tree-optimization/49093] New: " arthur.j.odwyer at gmail dot com
2011-05-21 9:54 ` [Bug tree-optimization/49093] [4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-05-21 16:53 ` hjl.tools at gmail dot com
2011-05-31 7:42 ` irar at il dot ibm.com
2011-05-31 8:31 ` rguenther at suse dot de
2011-05-31 8:36 ` irar at il dot ibm.com
2011-05-31 8:54 ` rguenther at suse dot de [this message]
2011-05-31 9:10 ` irar at il dot ibm.com
2011-05-31 9:18 ` rguenther at suse dot de
2011-05-31 9:24 ` irar at il dot ibm.com
2011-05-31 12:46 ` irar at gcc dot gnu.org
2011-06-02 7:03 ` irar at gcc dot gnu.org
2011-06-02 7:12 ` irar at il dot ibm.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-49093-4-pztBHC9V8V@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).