Displaying 6 results from an estimated 6 matches for "addressspacealiasanalysis".
2015 Apr 21
2
[LLVMdev] Using an alias analysis pass
...20111010/129635.html>, so I based mine off his. And one year ago, Matthew O’Connor ran into a similar issue <http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-April/072427.html>, and I tried to use the solution that worked for him. The result code is this:
> namespace
> {
> struct AddressSpaceAliasAnalysis : public FunctionPass, public AliasAnalysis
> {
> static char ID;
> AddressSpaceAliasAnalysis() : FunctionPass(ID) {
> }
>
> virtual bool runOnFunction(Function& f) override
> {
> InitializeAliasAnalysis(this, &f.getParent()->getDataLayout());
>...
2013 Aug 12
2
[LLVMdev] Address space extension
...ifferent types may alias, but not
> different address spaces. Maybe this can be handled encoding as type only
> the
> address space information.
>
The alias analysis interface allows different implementations to be chained
together. So I would imagine this working as follows:
(1) The AddressSpaceAliasAnalysis pass (if enabled) looks for source-level
address space metadata and sees if a definitive answer can be established
(2) If result is may-alias, then check for target-dependent address space
aliasing
(3) If result is may-alias, then chain to the next implementation (either
TBAA or a more basic alias...
2013 Aug 12
0
[LLVMdev] Address space extension
...not
> different address spaces. Maybe this can be handled encoding as type only the
> address space information.
>
>
> The alias analysis interface allows different implementations to be chained
> together. So I would imagine this working as follows:
>
> (1) The AddressSpaceAliasAnalysis pass (if enabled) looks for source-level
> address space metadata and sees if a definitive answer can be established
> (2) If result is may-alias, then check for target-dependent address space aliasing
> (3) If result is may-alias, then chain to the next implementation (either TBAA
> or...
2013 Aug 12
2
[LLVMdev] Address space extension
...ress spaces. Maybe this can be handled encoding as type only the
>> address space information.
>>
>>
>> The alias analysis interface allows different implementations to be chained
>> together. So I would imagine this working as follows:
>>
>> (1) The AddressSpaceAliasAnalysis pass (if enabled) looks for source-level
>> address space metadata and sees if a definitive answer can be established
>> (2) If result is may-alias, then check for target-dependent address space aliasing
>> (3) If result is may-alias, then chain to the next implementation (either...
2013 Aug 12
0
[LLVMdev] Address space extension
On 08/12/2013 02:02 PM, Justin Holewinski wrote:
> On Mon, Aug 12, 2013 at 6:03 AM, Michele Scandale <michele.scandale at gmail.com
> <mailto:michele.scandale at gmail.com>> wrote:
>
> On 08/12/2013 12:44 AM, Michele Scandale wrote:
> > The idea is to extend the BasicAliasAnalysis to use addrspace modifier +
> target
> > information to decide
2013 Aug 12
2
[LLVMdev] Address space extension
On Mon, Aug 12, 2013 at 6:03 AM, Michele Scandale <
michele.scandale at gmail.com> wrote:
> On 08/12/2013 12:44 AM, Michele Scandale wrote:
> > The idea is to extend the BasicAliasAnalysis to use addrspace modifier +
> target
> > information to decide aliasing based on physical address spaces and
> create a
> > "MemorySpaceAliasAnalysis" for those case