From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: powerpc-g++ 4.2.4 problem casting long long to double
Date: Mon, 24 May 2010 11:25:29 -0700 [thread overview]
Message-ID: <20100524182529.GA28464@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1005241813190.5274@asterix.crazy-teaparty.dyndns.org>
On (24/05/10 18:36), Vitus Jensen wrote:
>
> Well, it generates the call to __floatdidf from inside cast() but
> that function is never called from main but replaced with the
> precomputed result. See attached assembler output, there is no call
> to _Z4castx.
yeah I see, its inlining the function.
>
> Hmm, I'm using angstrom with glibc. And I'm testing on the real
> device and saw that -mhard-float is implied by mcpu=603e. Using the
> FPU would certainly explain differences between qemu and the real
> thing. But __floatdidf is hard to understand, all macro. Is it
> really using the FPU?
Yeah that could be something to look at. In general if gcc is using
fp instruction to schedule then it might be using them.
You should try to find which libgcc is it linking to when using g++
and gcc. It could be that its linking in two different libgcc versions
secondly try to compile program statically and then run it.
Also try to generate the linker map file in faulty and good case.
try ldd on the binary on target and see if there is any difference
in libraries it is wanting
>
> Vitus
>
> PS, to crosscheck: is there a HOWTO for qemu and oe/ppc? And
> qemu_0.12.4 doesn't build here.
You could use qemu-native from OE if thats not the one failing.
there is a script in contrib/qemu/run-qemu.sh thus far. Although one day I should
do a write-up on wiki about various qemu machines in OE
Thx
-Khem
next prev parent reply other threads:[~2010-05-24 18:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 9:38 powerpc-g++ 4.2.4 problem casting long long to double Vitus Jensen
2010-05-19 11:21 ` Gary Thomas
2010-05-19 11:41 ` Vitus Jensen
2010-05-19 11:45 ` Gary Thomas
2010-05-19 15:46 ` Vitus Jensen
2010-05-19 16:48 ` Koen Kooi
2010-05-21 11:12 ` Vitus Jensen
2010-05-21 13:21 ` Vitus Jensen
2010-05-21 13:40 ` Vitus Jensen
2010-05-21 20:37 ` Khem Raj
2010-05-24 16:36 ` Vitus Jensen
2010-05-24 18:25 ` Khem Raj [this message]
2010-05-25 15:15 ` Vitus Jensen
2010-05-25 15:52 ` Khem Raj
2010-05-26 5:34 ` Vitus Jensen
2010-05-26 6:21 ` Khem Raj
2010-06-07 19:23 ` [STABLE] " Vitus Jensen
2010-06-09 12:13 ` [PATCH][STABLE] gcc-pacpake-cross.inc: Clean up do_install function massively (from Poky) Vitus Jensen
2010-06-09 13:17 ` Khem Raj
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=20100524182529.GA28464@gmail.com \
--to=raj.khem@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