Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Xerxes Rånby" <xerxes@zafena.se>
To: openembedded-devel@lists.openembedded.org
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: Openjdk shark and cacao VMs not working - armv4 LLVM symbol powf, version GLIBCXX_3.4 not, defined
Date: Fri, 23 Jul 2010 12:58:14 +0200	[thread overview]
Message-ID: <4C4975C6.5030405@zafena.se> (raw)
In-Reply-To: <AANLkTikeJTj01x057Rur8H0haeDehcVVPqaQzDLq2dd6@mail.gmail.com>

On 2010-07-22 17:15, Martin Jansa wrote:
> On Wed, Jul 21, 2010 at 4:20 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
>   
>> FYI:
>>
>> Tested on om-gta02 (armv4t) and only -zero seems to work (built from
>> yesterday oe.dev, waiting for todays fixes to built).
>>
>> SHR root@gojama ~ $ javac -zero Linpack.java
>> Warning: no leading - on line 43 of `/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg'
>> Warning: missing VM type on line 43 of `/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg'
>> Warning: no leading - on line 43 of `/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg'
>> Warning: missing VM type on line 43 of `/usr/lib/jvm/java-6-openjdk/jre/lib/arm/jvm.cfg'
>>     
> With current version jvm.cfg warnings are gone, but cacao and shark still fails
> SHR root@gojama ~ $ java -zero Linpack
> Mflops/s: 1.691  Time: 0.41 secs  Norm Res: 1.43  Precision:
> 2.220446049250313E-16
>   
We are quite happy with the current default zero vm in OE since we do
not have any open bugreports for it, it seems stable and nice. :)

> SHR root@gojama ~ $ java -cacao Linpack
> LOG: [0x40190000] md_signal_handler_sigill: Unknown illegal
> instruction 0xed1c5a06 at 0x441c2790
> LOG: [0x40190000] Aborting...
> Aborted
>   
This regression on armv4 and armv5 are most likely caused by the
"armv7" cacao compatible patches bundled with icedtea6-1.8.

I will check if i can see anything obvious and try to debug it.

> SHR root@gojama ~ $ java -shark Linpack
> dl failure on line 696Error: failed
> /usr/lib/jvm/java-6-openjdk/jre/lib/arm/shark/libjvm.so, because
> /usr/lib/libLLVMCodeGen.so: symbol powf, version GLIBCXX_3.4 not
> defined in file libstdc++.so.6 with link time reference
>   
It looks like a different (older?) libstdc++ are used on your phone
compared to whats got used during the build when linking LLVM.
It would be good to check if a LLVM "HelloWorld" can get executed on the
phone.

Please try this LLVM testcase on your phone and report if it work or not:
======== start of file hello.ll
@hello = internal global [12 x i8] c"Hello World\00"

declare i32 @puts(i8*)

define i32 @main() {
    %r = call i32 @puts( i8* getelementptr ([12 x i8]* @hello, i64 0,
i64 0) )
    ret i32 0
}
======== end of file hello.ll
and then execute the following two commands:
llvm-as hello.ll
lli hello.bc

its possible that you have to type
/usr/bin/llvm2.7/llvm-as hello.ll
/usr/bin/llvm2.7/lli hello.bc

If all goes well then you should see.. yes you guessed it:
HelloWorld

If it fail then try updating the libstdc++ to the same version used when
linking llvm.
check if libm are installed.

> Let me know if you want more info.
>   




  reply	other threads:[~2010-07-23 10:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19  9:37 Openjdk shark and cacao VMs not working Koen Kooi
2010-07-21 11:41 ` Openjdk shark and cacao VMs not working - shark fixed Xerxes Rånby
2010-07-21 14:20   ` Martin Jansa
2010-07-22 15:15     ` Martin Jansa
2010-07-23 10:58       ` Xerxes Rånby [this message]
2010-08-18 22:47         ` Openjdk shark and cacao VMs not working - armv4 LLVM symbol powf, version GLIBCXX_3.4 not, defined Stefan Ring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C4975C6.5030405@zafena.se \
    --to=xerxes@zafena.se \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox