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/37742] [4.4 Regression] ICE in vectorizer with restrict pointer
Date: Wed, 19 Nov 2008 17:45:00 -0000	[thread overview]
Message-ID: <20081119174350.7215.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37742-15353@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from rguenther at suse dot de  2008-11-19 17:43 -------
Subject: Re:  [4.4 Regression] ICE in vectorizer with
 restrict pointer

On Tue, 18 Nov 2008, jakub at gcc dot gnu dot org wrote:

> ------- Comment #18 from jakub at gcc dot gnu dot org  2008-11-18 20:13 -------
> Created an attachment (id=16719)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16719&action=view)
>  --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16719&action=view)
> incremental patch
> 
> This fixed matmul_i2.c, DR_BASE_ADDRESS wasn't in this case TYPE_RESTRICT, nor
> SSA_NAME, but POINTER_PLUS_EXPR, yet in the end was based on a restrict
> pointer.
> Unfortunately other matmul*.c stuff in libgfortran is still broken.  I'm
> wondering if the strict alias checking introduced in r140781 isn't too eager
> when restricted pointers are used...

It can/should be relaxed to do an alias_sets_conflict_p check instead of
the subset check.  No idea if that helps - but also the patch at
http://gcc.gnu.org/ml/gcc-patches/2008-11/msg00286.html should fix all
of the current issues (maybe not optimally though).

Note that I added the alias checks to catch wrong-code issues.

Richard.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37742


  parent reply	other threads:[~2008-11-19 17:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06  5:18 [Bug middle-end/37742] New: ICE when compile mpich2-1.1.0a1 linuxl4 at sohu dot com
2008-10-06 15:56 ` [Bug middle-end/37742] " rguenth at gcc dot gnu dot org
2008-10-06 16:22 ` linuxl4 at sohu dot com
2008-10-06 16:33 ` jakub at gcc dot gnu dot org
2008-10-07  5:03 ` linuxl4 at sohu dot com
2008-10-07  5:08 ` linuxl4 at sohu dot com
2008-10-07 20:47 ` pinskia at gcc dot gnu dot org
2008-10-07 21:05 ` [Bug middle-end/37742] [4.4 Regression] ICE in vectorizer with restrict pointer to struct pinskia at gcc dot gnu dot org
2008-10-07 21:06 ` pinskia at gcc dot gnu dot org
2008-10-09 20:52 ` [Bug middle-end/37742] [4.4 Regression] ICE in vectorizer with restrict pointer reichelt at gcc dot gnu dot org
2008-10-10  7:51 ` rguenth at gcc dot gnu dot org
2008-10-13 21:38 ` pinskia at gcc dot gnu dot org
2008-10-14 20:47 ` rguenth at gcc dot gnu dot org
2008-10-22  3:48 ` mmitchel at gcc dot gnu dot org
2008-11-05 12:18 ` rguenth at gcc dot gnu dot org
2008-11-05 12:19 ` rguenth at gcc dot gnu dot org
2008-11-06  1:24 ` linuxl4 at sohu dot com
2008-11-11  8:14 ` reichelt at gcc dot gnu dot org
2008-11-18 18:27 ` jakub at gcc dot gnu dot org
2008-11-18 20:14 ` jakub at gcc dot gnu dot org
2008-11-19 17:45 ` rguenther at suse dot de [this message]
2008-11-20 16:26 ` rguenth at gcc dot gnu dot org
2008-11-20 17:17 ` rguenth at gcc dot gnu dot org
2008-11-20 17:23 ` rguenth at gcc dot gnu dot org
2008-11-21 11:11 ` rguenth at gcc dot gnu dot org
2008-11-28 11:32 ` rguenth at gcc dot gnu dot org
2008-11-28 11:33 ` 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=20081119174350.7215.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).