Displaying 5 results from an estimated 5 matches for "remotetarget".
2012 Sep 12
2
[LLVMdev] [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-linux
- Host-incapable target on the JIT
e.g.) --build=--host=x86_64-linux ---target=i686-mingw32...
2012 Sep 13
1
[LLVMdev] [llvm-commits] [llvm] r160610 - /llvm/trunk/lib/ExecutionEngine/TargetSelect.cpp
...itectures don't match? If so, what about the case where host=x86_64-linux and target=x86_64-mingw32?
Basically, I don't think local JIT could execute other environments.
Both {i686|x86_64}-mingw32 are incompatible to Linux, at least.
It should be suppressed unless the target could run as RemoteTarget.
BTW, do you think -target i686-linux should run under x86_64 binary?
(I wish so, but it would involve some issues...)
> I'm modifying the MCJIT tests so that they will provide an explicit target triple on the run line. In the case where the host OS is Windows, I'm appending "-el...
2012 Sep 12
0
[LLVMdev] [llvm-commits] [llvm] r160610 - /llvm/trunk/lib/ExecutionEngine/TargetSelect.cpp
...sage-----
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-linux
- Host-incapable target on the JIT
e.g.) --build=--host=x86_64-linux ---target=i686-mingw32...
2012 Oct 05
0
[LLVMdev] Cross-compiling to x86_64-mingw-w64
...eter
-Wwrite-strings -o
/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/Release/bin/lli.exe
/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/tools/lli/Release/RecordingMemoryManager.o
/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/tools/lli/Release/RemoteTarget.o
/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/tools/lli/Release/lli.o
\
-lLLVMAsmParser -lLLVMBitReader -lLLVMX86CodeGen -lLLVMX86Desc
-lLLVMX86Info -lLLVMX86AsmPrinter -lLLVMX86Utils -lLLVMSelectionDAG
-lLLVMAsmPrinter -lLLVMMCParser -lLLVMInterpreter -lLLVMJIT
-lLLVMCodeG...
2015 Jul 29
1
[LLVMdev] Error when i am using command make -j4 command in cygwin to compile safecode
...m-nm (without symbols)
make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-nm'
make[2]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/lli'
make[3]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/lli/ChildTarget'
llvm[3]: Compiling ../RemoteTarget.cpp for Release+Asserts build
llvm[2]: ======= Finished Linking Release+Asserts Executable llvm-link (without symbols)
make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-link'
llvm[3]: Compiling ChildTarget.cpp for Release+Asserts build
make[2]: Entering directory '/...