[llvm-commits] [llvm] r147542 - in /llvm/trunk: autoconf/configure.ac cmake/config-ix.cmake configure include/llvm/Config/config.h.cmake include/llvm/Config/config.h.in include/llvm/Config/llvm-config.h.cmake include/llvm/Config/llvm-config.h.in

[Sebastian Pop]

On Wed, Jan 4, 2012 at 2:39 PM, Joerg Sonnenberger
<joerg at britannica.bec.de> wrote:
> On Wed, Jan 04, 2012 at 07:47:23PM -0000, Sebastian Pop wrote:
>> use getHostTriple instead of getDefaultTargetTriple in getClosestTargetForJIT
>>
>> Get back getHostTriple.
>>
>> For JIT compilation, use the host triple instead of the default
>> target: this fixes some JIT testcases that used to fail when the
>> compiler has been configured as a cross compiler.
>
> I think this is wrong. Can such changes please discussed before?

Yes, thanks for speaking up.
(For reference, on Dec 27 I have sent a message asking for comments
http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-December/046484.html )

> Strictly speaking, running e.g. i386-linux on x86_64-netbsd is a
> cross-compiler. It can never the less work.

I am sorry to not see all the details of your example,
could you please give more details?  So you have a cross compiler
hosted on x86_64-netbsd and targeting i386-linux.  When you run
LLVM as a JIT you would like it to run on the host x86_64-netbsd, right?
Then it also has to produce code for the host x86_64-netbsd, and not
for the target i386-linux, as I'm assuming that the include files are
different than your host OS.

Am I misunderstanding your example?
Thanks for clarifying your point.

Sebastian
--
Qualcomm Innovation Center, Inc is a member of Code Aurora Forum