Displaying 3 results from an estimated 3 matches for "targettriple_provided_by_lit".
2012 Sep 13
1
[LLVMdev] [llvm-commits] [llvm] r160610 - /llvm/trunk/lib/ExecutionEngine/TargetSelect.cpp
...e. I think that should be sufficient to make things work in the cases where the host triple and the target triple are compatible, and then I can suppress the cases where host and target aren't compatible in the lit.local.cfg file.
>
> Does that sound right?
Do you mean; "-mtriple=%{targettriple_provided_by_lit}-elf" ?
I think MCJIT may reinterpret the triple to be accepted by elf.
> My concern is that I don't quite know how to predict what will happen on some of the buildbots aside from checking something in and seeing what happens. Hopefully any obvious problems will be caught in code revi...
2012 Sep 12
0
[LLVMdev] [llvm-commits] [llvm] r160610 - /llvm/trunk/lib/ExecutionEngine/TargetSelect.cpp
Hi Takumi,
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?
I'm modifying the MCJIT tests so that they will
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
If JIT is unavailable for the default target, tests