Displaying 3 results from an estimated 3 matches for "r160610".
2012 Sep 12
2
[LLVMdev] [llvm-commits] [llvm] r160610 - /llvm/trunk/lib/ExecutionEngine/TargetSelect.cpp
...the JIT
e.g.) --build=--host=i686-linux --target=x86_64-linux
- Host-incapable target on the JIT
e.g.) --build=--host=x86_64-linux ---target=i686-mingw32
If JIT is unavailable for the default target, tests in
test/ExecutionEngine and unittests/ExecutionEngine/JIT should be
suppressed. My r160610 intended to tweak tests on cross targets (not
to suppress, but to appease).
I wonder if we should honor the triple in Module, though.
Feel free to update, unless breaking tests, thank you.
...Takumi
2012/9/12 Kaylor, Andrew <andrew.kaylor at intel.com>:
> Hi,
>
> I realize that...
2012 Sep 12
0
[LLVMdev] [llvm-commits] [llvm] r160610 - /llvm/trunk/lib/ExecutionEngine/TargetSelect.cpp
...isn't compatible with the host environment then it will just fail.
-Andy
-----Original Message-----
From: NAKAMURA Takumi [mailto:geek4civic at gmail.com]
Sent: Tuesday, September 11, 2012 5:13 PM
To: Kaylor, Andrew
Cc: llvm-commits at cs.uiuc.edu; llvmdev
Subject: Re: [llvm-commits] [llvm] r160610 - /llvm/trunk/lib/ExecutionEngine/TargetSelect.cpp
Andy,
Yes, it was wrong, as long as RemoteTarget is available for the target.
If you would revert it, please consider then;
- non-MCJIT stuff
- Running different environment on the JIT
e.g.) --build=--host=i686-linux --target=x86_64-lin...
2012 Sep 13
1
[LLVMdev] [llvm-commits] [llvm] r160610 - /llvm/trunk/lib/ExecutionEngine/TargetSelect.cpp
2012/9/13 Kaylor, Andrew <andrew.kaylor at intel.com>:
> I'm a bit confused as to what is supposed to happen in the cross building scenarios. For instance, if host=x86_64-linux and target=i686-mingw32, what should the MCJIT tests do? Should they be suppressed because the architectures don't match? If so, what about the case where host=x86_64-linux and target=x86_64-mingw32?