From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: bmei@broadcom.com (Bingfeng Mei)
Cc: gcc@gcc.gnu.org (gcc@gcc.gnu.org)
Subject: Re: Derive more alias information from named address space
Date: Mon, 19 Sep 2011 11:56:00 -0000 [thread overview]
Message-ID: <201109191155.p8JBtdw1002580@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <7FB04A5C213E9943A72EE127DB74F0ADD15FCB0108@SJEXCHCCR02.corp.ad.broadcom.com> from "Bingfeng Mei" at Sep 16, 2011 09:11:00 AM
Bingfeng Mei wrote:
> Therefore, A & B could only be disjoint, i.e., not aliased to each other.
> We should be able to write:
>
> if (MEM_ADDR_SPACE (mem) != MEM_ADDR_SPACE (x))
> {
> if (!targetm.addr_space.subset_p (MEM_ADDR_SPACE (mem), MEM_ADDR_SPACE (x))
> && !targetm.addr_space.subset_p (MEM_ADDR_SPACE (x), MEM_ADDR_SPACE (mem)))
> return 0;
> else
> return 1;
> }
>
> Is this correct?
Yes, this looks correct to me ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2011-09-19 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 16:11 Bingfeng Mei
2011-09-19 11:56 ` Ulrich Weigand [this message]
2011-09-19 11:58 ` Bingfeng Mei
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=201109191155.p8JBtdw1002580@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=bmei@broadcom.com \
--cc=gcc@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).