ASan device library functions (those starts with the prefix __asan_)
are at the moment undergoing through undesired optimizations due to
internalization. Hence, in order to avoid such undesired optimizations
on ASan device library functions, do not internalize them in the first
place.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp | ||
---|---|---|
520–522 | there are two asan device functions that don't start with "__asan_*" prefix, they are the following:
@b-sumner do we want to not internalize those functions? | |
llvm/test/CodeGen/AMDGPU/internalize.ll | ||
3 ↗ | (On Diff #375013) | Since, this is a asan related change, I think it would be beneficial if we have a lit test with -fgpu-sanitize option. |
llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp | ||
---|---|---|
520–522 | Yes, I think sanitizer_* should be handled similarly to asan_* |
llvm/lib/Target/AMDGPU/AMDGPUTargetMachine.cpp | ||
---|---|---|
520–522 | Sorry I forgot about the markup. I meant __sanitizer_* should be handled similarly to __asan_* |
I've marked this test folder as needing AMDGPU in https://reviews.llvm.org/rG8f9f959b99e1.
there are two asan device functions that don't start with "__asan_*" prefix, they are the following:
@b-sumner do we want to not internalize those functions?