public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dorit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/34330] -ftree-parallelize-loops=4 ICE with the vectorizer also
Date: Wed, 19 Dec 2007 09:38:00 -0000 [thread overview]
Message-ID: <20071219093801.22864.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34330-87@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from dorit at gcc dot gnu dot org 2007-12-19 09:38 -------
> This is a vectorizer vs not being able to run may_alias after it
can you please remind me why we can't run may_alias after the vectorizer? (and
what do you think can be done about it?)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34330
next prev parent reply other threads:[~2007-12-19 9:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 22:43 [Bug tree-optimization/34330] New: [4.3 Regression] IC-ftree-parallelize-loops=4 ICE jakub at gcc dot gnu dot org
2007-12-10 0:23 ` [Bug tree-optimization/34330] -ftree-parallelize-loops=4 ICE with the vectorizer also pinskia at gcc dot gnu dot org
2007-12-16 22:07 ` rakdver at gcc dot gnu dot org
2007-12-18 18:51 ` rakdver at gcc dot gnu dot org
2007-12-19 9:38 ` dorit at gcc dot gnu dot org [this message]
2007-12-19 9:46 ` jakub at gcc dot gnu dot org
2008-01-21 17:47 ` rakdver at gcc dot gnu dot org
2008-05-12 9:14 ` razya at il dot ibm dot com
2008-05-12 9:43 ` razya at il dot ibm dot com
2008-05-13 9:08 ` rguenth at gcc dot gnu dot org
2008-05-15 8:22 ` rguenth at gcc dot gnu dot org
2008-05-15 8:23 ` rguenth at gcc dot gnu dot org
2008-05-15 9:24 ` razya at il dot ibm dot com
2008-05-15 9:28 ` rguenth at gcc dot gnu dot org
2008-05-15 9:29 ` rguenth at gcc dot gnu dot org
2008-05-15 9:41 ` razya at il dot ibm dot com
2008-05-15 9:46 ` razya at il dot ibm dot com
2008-05-20 21:05 ` rguenth at gcc dot gnu dot org
2008-05-20 21:06 ` rguenth at gcc dot gnu dot 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=20071219093801.22864.qmail@sourceware.org \
--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).