Displaying 2 results from an estimated 2 matches for "089706".
2017 Mar 16
5
[RFC] Allow allocas to produce a non-0 address space pointer
...gain a DataLayout argument, and some intrinsics that currently don't support address spaces need to support them.
This has been implemented out of tree before before for CHERI.
This has also been proposed before but for different reasons: http://lists.llvm.org/pipermail/llvm-dev/2015-August/089706.html
My current proposal is more focused than the previous proposal. Instead of allowing specifying address spaces on individual allocas, this restricts it to one chosen address space specified in the datalayout. I think the work to support different address spaces per-alloca is a strict superset...
2020 May 27
2
Custom Instruction Cost Model to LLVM RISC-V Backend
Thanks a lot Henrik!
I figured following would mark a pointer to a specific address space:
#define __myaddrspace __attribute__((address_space(1)))
__myaddrspace int* data;
And, I was able to verify loads being annotated to be from addrspace 1 in
the generated IR. Would this work for automatic variables as well?
In regards to using this in the backend, do I have to just modify the
source, or