llvm dev - Jan 2013 - [LLVMdev] LLVM JIT machine detection

How does the LLVM JIT determine the ABI and architecture to generate
code for?

I ask because I have an armhf device (running Debian, sort of), except
the JIT is generating soft-float code. This isn't ABI compatible as
parameters are passed in the wrong registers, and so simply doesn't work.

Is this something that I, as an LLVM library user, should not need to
worry about (and therefore the fact that it doesn't work is a
misconfiguration of the LLVM Debian package), or should I be setting up
the JIT somehow?

-- 
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ 𝕻𝖍'𝖓𝖌𝖑𝖚𝖎 𝖒𝖌𝖑𝖜'𝖓𝖆𝖋𝖍 𝕮𝖙𝖍𝖚𝖑𝖍𝖚 𝕽'𝖑𝖞𝖊𝖍
𝖜𝖌𝖆𝖍'𝖓𝖆𝖌𝖑 𝖋𝖍𝖙𝖆𝖌𝖓.
│

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130125/1cae9c7a/attachment.sig>

It is controlled by the TargetTriple which tries to have a good default.  You
can explicitly sets it by using EngineBuilder::setEnvironment().

Cheers.

-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
Behalf Of David Given
Sent: Friday, January 25, 2013 10:31 AM
To: llvmdev at cs.uiuc.edu
Subject: [LLVMdev] LLVM JIT machine detection

How does the LLVM JIT determine the ABI and architecture to generate code for?

I ask because I have an armhf device (running Debian, sort of), except the JIT
is generating soft-float code. This isn't ABI compatible as parameters are
passed in the wrong registers, and so simply doesn't work.

Is this something that I, as an LLVM library user, should not need to worry
about (and therefore the fact that it doesn't work is a misconfiguration of
the LLVM Debian package), or should I be setting up the JIT somehow?

--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ │ 𝕻𝖍'𝖓𝖌𝖑𝖚𝖎
𝖒𝖌𝖑𝖜'𝖓𝖆𝖋𝖍 𝕮𝖙𝖍𝖚𝖑𝖍𝖚 𝕽'𝖑𝖞𝖊𝖍
𝖜𝖌𝖆𝖍'𝖓𝖆𝖌𝖑 𝖋𝖍𝖙𝖆𝖌𝖓.
│