https://github.com/weliveindetail closed
https://github.com/llvm/llvm-project/pull/77491
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
weliveindetail wrote:
Thanks for the quick review!
https://github.com/llvm/llvm-project/pull/77491
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
weliveindetail wrote:
Oh and this matches the default behavior in Orc host detection btw:
https://github.com/llvm/llvm-project/blob/release/17.x/llvm/lib/ExecutionEngine/Orc/JITTargetMachineBuilder.cpp#L35
https://github.com/llvm/llvm-project/pull/77491
_
https://github.com/vgvassilev approved this pull request.
Thank you for the patch, Stefan! Some of our downstream consumers use that
flag for exactly these reasons.
LGTM!
https://github.com/llvm/llvm-project/pull/77491
___
cfe-commits mailing list
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Stefan Gränitz (weliveindetail)
Changes
We can pass `-mcpu=native` to the clang driver to let it consider the host CPU
when choosing the compile target for `clang-repl`. We can already achieve this
behavior with `clang-repl -Xcc -mcpu=nat
https://github.com/weliveindetail created
https://github.com/llvm/llvm-project/pull/77491
We can pass `-mcpu=native` to the clang driver to let it consider the host CPU
when choosing the compile target for `clang-repl`. We can already achieve this
behavior with `clang-repl -Xcc -mcpu=native`,
