Displaying 3 results from an estimated 3 matches for "newptrvt".
Did you mean:
newport
2012 Aug 25
0
[LLVMdev] FW: RFC: Supporting different sized address space arithmetic
...f
TargetLowering::getValueType() doesn't work for arbitrary address
spaces, you should fix it.
I think my earlier comments about getIntPtrConstant still hold:
instead of "DAG.getIntPtrConstant(Offset, addrSpace)", you can just
write "DAG.getConstant(Offset, PtrTy)".
+ EVT NewPtrVT = TLI.getPointerTy(dyn_cast<PointerType>(
+ SV->getType())->getAddressSpace());
+ if (PtrVT != NewPtrVT) {
+ // Check to see if we want to change the size of the pointer
+ // based on the address space and if so extend or truncate the pointer.
+ Ptr = DAG.getSExtOrTrunc...
2012 Aug 24
5
[LLVMdev] FW: RFC: Supporting different sized address space arithmetic
> -----Original Message-----
> From: Villmow, Micah
> Sent: Friday, August 24, 2012 2:56 PM
> To: 'Eli Friedman'
> Cc: LLVM Developers Mailing List
> Subject: RE: [LLVMdev] RFC: Supporting different sized address space
> arithmetic
>
> Eli,
> There is a patch that implements the beginning what I think is the
> correct approach to support the backend
2012 Aug 30
2
[LLVMdev] FW: RFC: Supporting different sized address space arithmetic
...esn't work for arbitrary address
> spaces, you should fix it.
>
> I think my earlier comments about getIntPtrConstant still hold:
> instead of "DAG.getIntPtrConstant(Offset, addrSpace)", you can just
> write "DAG.getConstant(Offset, PtrTy)".
>
> + EVT NewPtrVT = TLI.getPointerTy(dyn_cast<PointerType>(
> + SV->getType())->getAddressSpace());
> + if (PtrVT != NewPtrVT) {
> + // Check to see if we want to change the size of the pointer
> + // based on the address space and if so extend or truncate the
> pointer.
>...