[llvm-dev] [RFC] BasicAA considers address spaces?

Hal Finkel via llvm-dev
Sat, 08 Aug 2015 01:30:00 -0000

----- Original Message -----
> From: "Matt Arsenault" <Matthew.Arsenault at amd.com>
> To: "Hal Finkel" <hfinkel at anl.gov>, "Justin
Holewinski" <jholewinski at nvidia.com>
> Cc: "Jingyue Wu" <jingyue at google.com>, llvm-dev at
lists.llvm.org, "Eli Bendersky" <eliben at google.com>,
"Xuetian Weng"
> <xweng at google.com>
> Sent: Friday, August 7, 2015 8:21:27 PM
> Subject: Re: [RFC] BasicAA considers address spaces?
>
> On 08/07/2015 06:13 PM, Hal Finkel wrote:
> > But you seem to be implying that you'll use different address
> > spaces
> > at the IR level, but that these address spaces will be changed
> > prior
> > to the target seeing them? Or that the target will internally map
> > them
> > all to address space 0 (instead of aborting). If the target knows
> > to
> > do this mapping, it can also understand the aliasing, no?
>
> clang performs the mapping from source address space to target
> address
> space. See AddrSpaceMap in clang's TargetInfo

But then that's too late for any address-space-based metadata. What you need
is just aliasing metadata, which is another matter (and, to some extent, we
already have).

 -Hal

>

--
Hal Finkel
Assistant Computational Scientist
Leadership Computing Facility
Argonne National Laboratory