shark improperly linked against llvm 2.4 (and first steps on ARM)

[Robert Schuster]

Hi,
I was hunting down a problem where I could not get shark to run on ARM
with llvm 2.4.
It turned out that the TargetMachineRegistry did not contain an entry
for my machine at runtime. This is caused by not linking
LLVMArmCodeGen.o into the final executable and that I is caused by
IcedTea's configure script using 'engine' as the sole component when
retrieving LLVM_LIBS.

This is what it looks for 'engine' on my machine:

rob at linkist:/$ llvm-config --libs engine
/home/rob/oe/beagle/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/lib/LLVMInterpreter.o
/home/rob/oe/beagle/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/lib/LLVMExecutionEngine.o
/home/rob/oe/beagle/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/lib/LLVMJIT.o
-lLLVMCodeGen -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa
-lLLVMAnalysis -lLLVMTarget -lLLVMCore -lLLVMSupport -lLLVMSystem

This is what it looks for 'nativecodegen' on my machine:

rob at linkist:/$ llvm-config --libs nativecodegen
/home/rob/oe/beagle/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/lib/LLVMARMCodeGen.o
-lLLVMSelectionDAG -lLLVMCodeGen -lLLVMScalarOpts -lLLVMTransformUtils
-lLLVMipa -lLLVMAnalysis -lLLVMTarget -lLLVMCore -lLLVMSupport -lLLVMSystem

I am now using 'engine nativecodegen' as the requested components and
this works fine. I retrieved those components by looking at what is
needed to link llvm's lli program which runs fine.

The reason for why linking in that module is neccessary is because those
.o files contain static elements which register themselves to the
TargetMachineRegistry when the elements are initialized.
See include/llvm/Target/TargetMachineRegistry.h (search RegisterTarget)
for details.

A quick comparison with the llvm-config that Debian provides (2.2)
reveals that 'nativecodegen' is not available with that version. So you
probably need to declare a minimum supported llvm version. In case
'nativecodegen' should be used that would be 2.4.

For ARM llvm and/or shark seems not to be 100% up to par ....

root at beagleboard:~# java -version
java version "1.6.0_0"
IcedTea6 1.4 Runtime Environment (build 1.6.0_0-b14)
OpenJDK Shark VM (build 14.0-b08, mixed mode)
java:
/home/rob/oe/beagle/tmp/work/armv7a-angstrom-linux-gnueabi/llvm-2.4-r0/llvm-2.4/include/llvm/CodeGen/MachineOperand.h:251:
int64_t llvm::MachineOperand::getImm() const: Assertion `isImm() &&
"Wrong MachineOperand accessor"' failed.
Aborted

... but some simple apps already work:

root at beagleboard:~# java HelloWorld
Hello World!
java:
/home/rob/oe/beagle/tmp/work/armv7a-angstrom-linux-gnueabi/llvm-2.4-r0/llvm-2.4/include/llvm/CodeGen/MachineOperand.h:251:
int64_t llvm::MachineOperand::getImm() const: Assertion `isImm() &&
"Wrong MachineOperand accessor"' failed.
Aborted

Do you think that assertion is a shark or an llvm issue?

Regards
Robert

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20090125/221c9352/signature.asc