Displaying 2 results from an estimated 2 matches for "d34983".
2017 Jul 11
6
RFC: Harvard architectures and default address spaces
...ion objects because at that point in the pipeline, we do not
know the target architecture.
Because of this, I’d like to extend TargetTransformInfo with hooks that
like getSwitchTableAddressSpace(), getFunctionAddressSpace(). I have
already got a WIP patch for this here <https://reviews.llvm.org/D34983>.
Once we have that information available to TargetTransformInfo, I propose
we add a pass (very early in the codegen pipeline) that sets the address
space of all functions to whatever value is specified in the hooks.
This works well because we don’t let frontends specify address space on
funct...
2017 Jul 11
2
RFC: Harvard architectures and default address spaces
...hat point in the pipeline, we do not
> know the target architecture.
>
> Because of this, I’d like to extend TargetTransformInfo with hooks that
> like getSwitchTableAddressSpace(), getFunctionAddressSpace(). I have
> already got a WIP patch for this here <https://reviews.llvm.org/D34983>.
>
> Once we have that information available to TargetTransformInfo, I propose
> we add a pass (very early in the codegen pipeline) that sets the address
> space of all functions to whatever value is specified in the hooks.
>
> This works well because we don’t let frontends sp...