Displaying 2 results from an estimated 2 matches for "constant_address".
2019 Feb 01
2
[RFC] arm64_32: upstreaming ILP32 support for AArch64
> On Feb 1, 2019, at 2:25 PM, Eli Friedman via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
>
> I was thinking of a model something like this: 32-bit pointers are addrspace 0, 64-bit pointers are addrspace 1. ISD::LOAD/STORE in addrspace 0 are not legal: they're custom-lowered to operations in addrspace 1. (An addrspacecast from 0 to 1 is just zero-extension.) At that
2012 Jul 16
3
[LLVMdev] RFC: LLVM incubation, or requirements for committing new backends
...o
> +/// a seperate piece of memory that is unique from other
> +/// memory locations.
> +namespace AMDILAS {
> +enum AddressSpaces {
> + PRIVATE_ADDRESS = 0, // Address space for private memory.
> + GLOBAL_ADDRESS = 1, // Address space for global memory (RAT0, VTX0).
> + CONSTANT_ADDRESS = 2, // Address space for constant memory.
> + LOCAL_ADDRESS = 3, // Address space for local memory.
> + REGION_ADDRESS = 4, // Address space for region memory.
> + ADDRESS_NONE = 5, // Address space for unknown memory.
> + PARAM_D_ADDRESS = 6, // Address space for direct...