[PATCH] D131345: [RISC-V][HWASAN] Enable HWASAN for RISC-V architecture

smd created this revision. Herald added subscribers: Enna1, sunshaoce, VincentWu, luke957, vkmr, luismarques, sameer.abuasal, s.egerton, Jim, PkmX, rogfer01, shiva0217, kito-cheng, simoncook, arichardson, mgorny. Herald added a project: All. smd edited the summary of this revision. smd added revi

[PATCH] D131345: [RISC-V][HWASAN] Enable HWASAN for RISC-V architecture

kito-cheng added a comment. I guess we should checking `J` extension is enabled somewhere when user trying to enable HWASAN? or checking that at HWASAN library at run-time? otherwise my understanding is user will get crash when enabling HWASAN if linux and/or HW don't support that? Repository

[PATCH] D131345: [RISC-V][HWASAN] Enable HWASAN for RISC-V architecture

smd added a comment. In D131345#3712814 , @kito-cheng wrote: > I guess we should checking `J` extension is enabled somewhere when user > trying to enable HWASAN? or checking that at HWASAN library at run-time? > otherwise my understanding is user will

[PATCH] D131345: [RISC-V][HWASAN] Enable HWASAN for RISC-V architecture

kito-cheng accepted this revision. kito-cheng added a comment. > It relies on a runtime check: during init runtime makes > PR_{SET,GET}_TAGGED_ADDR_CTRL calls and if they're not supported, it fails > with an error. So burden of checking if J extension is present is on Linux > kernel. Sounds go

[PATCH] D131345: [RISC-V][HWASAN] Enable HWASAN for RISC-V architecture

This revision was automatically updated to reflect the committed changes. Closed by commit rG2eac70c1084c: [RISC-V][HWASAN] Enable HWASAN for RISC-V architecture (authored by smd). Changed prior to commit: https://reviews.llvm.org/D131345?vs=450579&id=482841#toc Repository: rG LLVM Github Mo