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 middle-end/37491] [4.4 Regression] Revision 140257 causes vectorizer tests failures
Date: Mon, 15 Sep 2008 09:40:00 -0000 [thread overview]
Message-ID: <20080915093905.1602.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37491-682@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from rguenther at suse dot de 2008-09-15 09:39 -------
Subject: Re: [4.4 Regression] Revision 140257 causes
vectorizer tests failures
On Mon, 15 Sep 2008, irar at il dot ibm dot com wrote:
>
>
> ------- Comment #9 from irar at il dot ibm dot com 2008-09-15 09:35 -------
> (In reply to comment #8)
> > Well, I think the ICE happens because for stores we call
> > vect_create_data_ref_ptr with an explicit vector type which is based on
> > the rhs, not the lhs. The ICE should never occur if we based the
> > vector type on the lhs.
>
> No, no. The ICE occurs when we base the vector type on the lhs!
> vector void (*<T48f>) (int) * ivtmp.30;
> vector void (*<T49a>) (int_t) vect_cst_.23;
>
> *ivtmp.30_13 = vect_cst_.23_9;
> The rhs and the lhs are not the same (and do not alias).
The rhs ans the lhs do not need to alias. The important thing is that
the *ivtmp.30_13 aliases the original scalar store - if *ivtmp.30_13
is based on the scalar lhs type this will be always the case.
I am going to have a look myself (not right now, but somewhen this
week) - feel free to assign this bug to me for now.
Thanks,
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37491
next prev parent reply other threads:[~2008-09-15 9:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 0:33 [Bug middle-end/37491] New: " hjl dot tools at gmail dot com
2008-09-13 12:42 ` [Bug middle-end/37491] " rguenth at gcc dot gnu dot org
2008-09-14 7:02 ` irar at il dot ibm dot com
2008-09-14 9:33 ` rguenth at gcc dot gnu dot org
2008-09-14 10:05 ` irar at il dot ibm dot com
2008-09-14 10:37 ` rguenther at suse dot de
2008-09-14 12:06 ` irar at il dot ibm dot com
2008-09-14 12:54 ` rguenther at suse dot de
2008-09-15 9:13 ` irar at il dot ibm dot com
2008-09-15 9:24 ` rguenther at suse dot de
2008-09-15 9:36 ` irar at il dot ibm dot com
2008-09-15 9:40 ` rguenther at suse dot de [this message]
2008-09-17 10:11 ` rguenth at gcc dot gnu dot org
2008-09-17 11:44 ` rguenth at gcc dot gnu dot org
2008-09-17 11:45 ` rguenth at gcc dot gnu dot org
2008-09-22 9:25 ` irar at il dot ibm dot com
2008-09-22 10:08 ` rguenth at gcc dot gnu dot org
2008-09-22 10:34 ` irar at il dot ibm dot com
2008-09-22 11:16 ` rguenther at suse dot de
2008-09-22 11:49 ` rguenth at gcc dot gnu dot org
2008-09-22 12:33 ` irar at il dot ibm dot com
2008-09-22 12:42 ` irar at il dot ibm dot com
2008-09-30 10:39 ` 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=20080915093905.1602.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).