Palmer Dabbelt 52e7c52d2d RISC-V: Stop relying on GCC's register allocator's hueristics ... GCC allows users to hint to the register allocation that a variable should be placed in a register by using a syntax along the lines of function(...) { register long in_REG __asm__("REG"); } We've abused this a bit throughout the RISC-V port to access fixed registers directly as C variables. In practice it's never going to blow up because GCC isn't going to allocate these registers, but it's not a well defined syntax so we really shouldn't be relying upon this. Luckily there is a very similar but well defined syntax that allows us to still access these registers directly as C variables, which is to simply declare the register variables globally. For fixed variables this doesn't change the ABI. LLVM disallows this ambiguous syntax, so this isn't just strictly a formatting change. Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>		2020-03-03 10:28:13 -08:00
..
asm	RISC-V: Stop relying on GCC's register allocator's hueristics	2020-03-03 10:28:13 -08:00
uapi/asm	riscv, bpf: Add missing uapi header for BPF_PROG_TYPE_PERF_EVENT programs	2019-12-19 16:03:31 +01:00