public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian dot pop at cri dot ensmp dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/24262] [4.1 Regression] ICE: verify_ssa failed with -O -msse2 -ftree-vectorize
Date: Wed, 12 Oct 2005 16:26:00 -0000 [thread overview]
Message-ID: <20051012162625.674.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24262-8707@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from sebastian dot pop at cri dot ensmp dot fr 2005-10-12 16:26 -------
Subject: Re: [4.1 Regression] ICE: verify_ssa failed with -O -msse2
-ftree-vectorize
irar at il dot ibm dot com wrote:
> Here scev analyzer calculates the evolution of 'D.1703_5 * 2 + i_15',
> where 'D.1703_5 = i_15/2'. Scev doesn't handle division, therefore
> for D.1703_5 we get unknown scev, but then it's combined with the
> rest of the expression, erroneously leading to {D.1703_5*2, +, 1}.
>
I don't follow: "unknown + something" should be folded into "unknown",
not {D.1703_5*2, +, 1}_x: if D.1703_5 is defined in loop_x, it
potentially has an evolution in loop_x. I'm thinking that a test:
if (!expr_invariant_in_loop_p (loop, CHREC_LEFT (chrec)))
then give up with this case,
would solve this bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24262
next prev parent reply other threads:[~2005-10-12 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 18:52 [Bug tree-optimization/24262] New: " ferdinandw+gcc at gmail dot com
2005-10-07 19:27 ` [Bug tree-optimization/24262] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-10-12 7:23 ` dorit at il dot ibm dot com
2005-10-12 9:00 ` irar at il dot ibm dot com
2005-10-12 16:26 ` sebastian dot pop at cri dot ensmp dot fr [this message]
2005-10-12 16:53 ` sebastian dot pop at cri dot ensmp dot fr
2005-10-13 11:53 ` cvs-commit at gcc dot gnu dot org
2005-10-13 13:46 ` pinskia at gcc dot gnu dot org
2005-10-24 9:38 ` irar 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=20051012162625.674.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).