Displaying 2 results from an estimated 2 matches for "d56003".
Did you mean:
56003
2018 Dec 21
2
[RFC] Allocatable Global Register Variables for ARM
...{i32 1, !"fixed_reg.foo", !"r4"}
---
This is achieved via a modification to CodeGenModule::EmitGlobal. In addition, there are some changes relating
to specifying valid global registers (by adding an Arm override for isValidGlobalRegister),
Draft Patch: https://reviews.llvm.org/D56003
LLVM Changes
----------------------
In the LLVM backend we can then use the module flags to add any (valid) specified global registers to the
reserved reg list (getReservedRegs). In addition, to satisfy the second use-case*, we use the flags to remove
any (valid) global registers from the list of...
2019 Jan 04
2
[RFC] Allocatable Global Register Variables for ARM
...{i32 1, !"fixed_reg.foo", !"r4"}
---
This is achieved via a modification to CodeGenModule::EmitGlobal. In addition, there are some changes relating
to specifying valid global registers (by adding an Arm override for isValidGlobalRegister),
Draft Patch: https://reviews.llvm.org/D56003
Why did you decide to use global metadata here? For AArch64, we use a target feature instead, to implement roughly equivalent functionality (the reserve-x18 feature, to implement -ffixed-x18).
Making a global register declaration have side-effects never made sense, IMO; on the surface, it'...