aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Target/WebAssembly/WebAssemblyTargetMachine.cpp
diff options
context:
space:
mode:
authorJoseph Huber <huberjn@outlook.com>2025-09-11 11:06:20 -0500
committerGitHub <noreply@github.com>2025-09-11 11:06:20 -0500
commit05bbb947cf3b263c9f6e6908de9b9ec04f9cca4b (patch)
tree88c13d99082f3de9074098cde83989e8aa9006a7 /llvm/lib/Target/WebAssembly/WebAssemblyTargetMachine.cpp
parent5437d90bb72e38ad767dd2e130d23675130a7857 (diff)
downloadllvm-05bbb947cf3b263c9f6e6908de9b9ec04f9cca4b.zip
llvm-05bbb947cf3b263c9f6e6908de9b9ec04f9cca4b.tar.gz
llvm-05bbb947cf3b263c9f6e6908de9b9ec04f9cca4b.tar.bz2
[X86] Relax AVX ABI warning on internal functions (#157570)
Summary: The vector target should be able to handle vector sizes that are multiples of the native size, this is useful for implementing math routines that want to temporarily use a high precision for example. However, currently this will emit a warning on x86 if any function calls are involved. https://godbolt.org/z/dK7hGndYh. I believe that we should be able to relax the ABI restriction if the functions are completely internal and there were no explicitly states attributes to conflict. Because the ABI is not exported outside the TU we should be safe to assume that it won't bite us. In the case that one call has no features and other does, that will still cause an error. I may be wrong on this assumption however. Fixes: https://github.com/llvm/llvm-project/issues/128361
Diffstat (limited to 'llvm/lib/Target/WebAssembly/WebAssemblyTargetMachine.cpp')
0 files changed, 0 insertions, 0 deletions