From: Razya Ladelsky <RAZYA@il.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Guenther <richard.guenther@gmail.com>
Subject: Re: [PATCH, take 2] Fix PR tree-optimization/49960 ,Fix self data dependence
Date: Mon, 21 Nov 2011 14:24:00 -0000 [thread overview]
Message-ID: <OF7EA72A95.B3E25FE6-ONC225794F.004B41E0-C225794F.004C0361@il.ibm.com> (raw)
In-Reply-To: <20111121125707.GG27242@tyan-ft48-01.lab.bos.redhat.com>
gcc-patches-owner@gcc.gnu.org wrote on 21/11/2011 02:57:07 PM:
> From: Jakub Jelinek <jakub@redhat.com>
> To: Razya Ladelsky/Haifa/IBM@IBMIL
> Cc: Richard Guenther <richard.guenther@gmail.com>, GCC Patches <gcc-
> patches@gcc.gnu.org>
> Date: 21/11/2011 02:57 PM
> Subject: Re: [PATCH, take 2] Fix PR tree-optimization/49960 ,Fix
> self data dependence
> Sent by: gcc-patches-owner@gcc.gnu.org
>
> On Tue, Nov 15, 2011 at 12:31:39PM +0200, Razya Ladelsky wrote:
> > This patch fixes the failures described in
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49960
> > It also fixes bzips when run with autopar enabled.
>
> Sorry, I've been away and couldn't react to this earlier, but the patch
> looks wrong to me. The reason why I've been calling
compute_self_dependence
> from the gather handling code is to do there what we did for normal data
> references in compute_all_dependences, except for the affine stuff.
Hi Jakub,
what do you mean by 'except for the affine stuff'?
Before having this patch, compute_self_depepndence just marked the
distance zero
and returned, while now it calls compute_affine_dependence.
So I think you do get the right outcome now.
> So, when compute_all_dependences no longer calls it, neither should
> vect_analyze_data_refs.
So do you want to replace it with the call to compute_affine_dependence?
Thanks,
Razya
>
> Jakub
>
next prev parent reply other threads:[~2011-11-21 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 7:21 [patch] " Razya Ladelsky
2011-10-17 8:53 ` Richard Guenther
[not found] ` <OF746BCB18.CF82809F-ONC225792E.0051CE3F-C225792E.00564975@il.ibm.com>
[not found] ` <CAFiYyc2ykFPCW8A8vW=f5UbNa7zFRQObwL13D9ioXjCd_em9pQ@mail.gmail.com>
2011-10-21 9:26 ` Fwd: " Richard Guenther
2011-11-15 15:13 ` [PATCH, take 2] " Razya Ladelsky
2011-11-15 18:54 ` Richard Guenther
2011-11-21 13:32 ` Jakub Jelinek
2011-11-21 14:24 ` Razya Ladelsky [this message]
2011-11-21 14:54 ` Jakub Jelinek
2011-11-21 15:43 ` Razya Ladelsky
2011-11-21 16:13 ` Jakub Jelinek
2011-11-21 17:25 ` Razya Ladelsky
2011-11-21 18:26 ` Jakub Jelinek
2011-11-24 15:48 ` Razya Ladelsky
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=OF7EA72A95.B3E25FE6-ONC225794F.004B41E0-C225794F.004C0361@il.ibm.com \
--to=razya@il.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.com \
/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).