search for: isaddressspacesupported

Displaying 5 results from an estimated 5 matches for "isaddressspacesupported".

2013 Aug 11
2
[LLVMdev] Address space extension
...08:41 AM, Micah Villmow wrote: > How about this as a solution. > > Add one hook into TargetInstrInfo, and one into TargetISelLowering. > > 1) getAddressSpaceRelation(unsigned AS1, unsigned AS2) - Returns either disjoint, subset, superset, equal. Function defaults to equal. > 2) isAddressSpaceSupported(unsigned AS) - Returns true if supported, false otherwise. Function defaults to false for all non-zero AS. > > These could be used by IR passes to optimized(#1) and legalization(#2). It requires no changes by backends that do not want to support multiple address spaces and extremely minimal...
2013 Aug 11
0
[LLVMdev] Address space extension
How about this as a solution. Add one hook into TargetInstrInfo, and one into TargetISelLowering. 1) getAddressSpaceRelation(unsigned AS1, unsigned AS2) - Returns either disjoint, subset, superset, equal. Function defaults to equal. 2) isAddressSpaceSupported(unsigned AS) - Returns true if supported, false otherwise. Function defaults to false for all non-zero AS. These could be used by IR passes to optimized(#1) and legalization(#2). It requires no changes by backends that do not want to support multiple address spaces and extremely minimal and reason...
2013 Aug 11
0
[LLVMdev] Address space extension
...gt; > How about this as a solution. > > > > Add one hook into TargetInstrInfo, and one into TargetISelLowering. > > > > 1) getAddressSpaceRelation(unsigned AS1, unsigned AS2) - Returns either > disjoint, subset, superset, equal. Function defaults to equal. > > 2) isAddressSpaceSupported(unsigned AS) - Returns true if supported, > false otherwise. Function defaults to false for all non-zero AS. > > > > These could be used by IR passes to optimized(#1) and legalization(#2). > It requires no changes by backends that do not want to support multiple > address space...
2013 Aug 11
2
[LLVMdev] Address space extension
...as a solution. > > > > Add one hook into TargetInstrInfo, and one into TargetISelLowering. > > > > 1) getAddressSpaceRelation(unsigned AS1, unsigned AS2) - Returns either > disjoint, subset, superset, equal. Function defaults to equal. > > 2) isAddressSpaceSupported(unsigned AS) - Returns true if supported, false > otherwise. Function defaults to false for all non-zero AS. > > > > These could be used by IR passes to optimized(#1) and legalization(#2). It > requires no changes by backends that do not want to support multiple ad...
2013 Aug 11
5
[LLVMdev] Address space extension
Shortening the email chain. > Using this example or another equivalent example can you explain me what is > your variant of the solution? How would you solve the current absence of > information in the case of X86 target? [Micah Villmow] I understand what you are trying to do. I don't see the need, only added complexity for little gain, to involve the backends. Everything you are