public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <richard.guenther@gmail.com>
To: gcc@gcc.gnu.org
Cc: Sebastian Pop <sebpop@gmail.com>, Li Feng <nemokingdom@gmail.com>,
	 	gcc-graphite <gcc-graphite@googlegroups.com>
Subject: Re: How could I get alias set information from data_reference_p
Date: Wed, 15 Jul 2009 20:49:00 -0000	[thread overview]
Message-ID: <84fc9c000907151348s41395cc5u6cfacb60cde78bfa@mail.gmail.com> (raw)
In-Reply-To: <84fc9c000907151346r58239f06u318b55fe72ae0038@mail.gmail.com>

On Wed, Jul 15, 2009 at 10:46 PM, Richard
Guenther<richard.guenther@gmail.com> wrote:
> On Wed, Jul 15, 2009 at 9:15 PM, Tobias
> Grosser<grosser@fim.uni-passau.de> wrote:
>>> A note on Lis final graph algorithm.  I don't understand why you want
>>> to allow data-references to be part of multiple alias-sets?  (Of course
>>> I don't know how you are going to use the alias-sets ...)
>>
>> Just to pass more information to Graphite. The easiest example might be
>> something like
>>
>> A -- B -- C
>>
>> if we have
>>
>> AS1 = {A,B}
>> AS2 = {B,C}
>>
>> we know that A and C do not alias and therefore do not have any
>
> No, from the above you _don't_ know that.  How would you arrive
> at that conclusion?

What I want to say is that, if  A -- B -- C is supposed to be the alias graph
resulting from querying the alias oracle for the pairs (A, B), (A, C), (B, C)
then this is a result that will never occur.  Because if (A, B) is true
and (B, C) is true then (A, C) will be true as well.

Richard.

>> dependencies. If we put A,B,C in one big set we can not say this.
>
> But that is what would be correct. (?)
>
> Richard.
>

  reply	other threads:[~2009-07-15 20:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14  6:01 Li Feng
2009-07-14  8:54 ` Richard Guenther
2009-07-14  9:12   ` Li Feng
2009-07-14  9:40     ` Richard Guenther
2009-07-14 15:14       ` Sebastian Pop
2009-07-14 15:26         ` Richard Guenther
2009-07-14 16:03           ` Sebastian Pop
2009-07-14 16:09             ` Sebastian Pop
2009-07-14 21:34               ` Richard Guenther
2009-07-15  7:59                 ` Li Feng
2009-07-15 11:02                 ` Tobias Grosser
2009-07-15 11:26                   ` Richard Guenther
2009-07-15 19:16                     ` Tobias Grosser
2009-07-15 20:46                       ` Richard Guenther
2009-07-15 20:49                         ` Richard Guenther [this message]
     [not found]                         ` <15137_1247690941_4A5E40BC_15137_586_1_84fc9c000907151348s41395cc5u6cfacb60cde78bfa@mail.gmail.com>
2009-07-15 23:16                           ` Tobias Grosser
2009-07-16  8:39                             ` Richard Guenther
2009-07-16  9:00                               ` Li Feng
2009-07-16  9:16                                 ` Richard Guenther
2009-07-16 15:45                                 ` Daniel Berlin
2009-07-16 16:04                                   ` Sebastian Pop
2009-07-17  1:36                                   ` Li Feng

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=84fc9c000907151348s41395cc5u6cfacb60cde78bfa@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-graphite@googlegroups.com \
    --cc=gcc@gcc.gnu.org \
    --cc=nemokingdom@gmail.com \
    --cc=sebpop@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).