From: Rex Ashbaugh <rexa@xeratech.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with iperf
Date: Thu, 28 Feb 2008 08:33:19 -0700 [thread overview]
Message-ID: <6311fe0b0802280733q17996f0n14e5cedade44df78@mail.gmail.com> (raw)
In-Reply-To: <337959.75035.qm@web23402.mail.ird.yahoo.com>
Also, check how your cross compiler is configured for floating point
handling..
http://www.arm.linux.org.uk/mailinglists/faq.php
3. I feel really confused about what's the difference with gcc
soft-float support and the kernel NWFPE/FastFPE support?
[31 January 2004 - np]
Scenario 1 (hard-float): The compiler emits opcodes designed to
be used with a hardware floating point coprocessor (FPU). The
FPU usually has a set of extra registers for its use, and the
compiler may as well pass floating point argument to functions
through those registers. This is of course the best performing
solution when a real hardware FPU is used.
Scenario 2 (soft-float): the compiler converts floating point
operations into function calls and a special library is used to
provide all functions performing the required operations, all
in software with no FPU instructions at all. There is obviously
no extra floating point registers available in this case,
therefore all FP arguments to functions have to be passed
through standard registers or on the stack. This is of course
the best performing solution when no hardware FPU is available,
given that the library implementing the FP operations is
optimally coded.
Now, unfortunately, the default on ARM Linux has traditionally
been set to have the compiler use hard-float, even if ARM Linux
never ran on any ARM CPU with a real hardware FPU. The CPU is
therefore raising the invalid instruction exception each time
some FPU opcode is encountered. Then the kernel traps that
exception, looks at the given FPU instruction and emulates it
in software. But here not only the kernel must perform the FP
operation, it must emulates the whole hardware FPU as well.
That's what NWFPE or FastFPE are doing. This is obviously the
worst performing arrangement that can be due to the exception
trap and emulation overhead
On 2/28/08, Nicola Salvemini <nicolasalvemini@yahoo.it> wrote:
>
> Hi Rex,
>
> Yes I tried with the previous version (2.0.1) of iperf, bat I had same
> results.
> I'm waiting for a replay from iperf maintainer.
> Best regards,
>
> Nicola.
>
> ----- Messaggio originale -----
> Da: Rex Ashbaugh <rexa@xeratech.com>
> A: Nicola Salvemini <nicolasalvemini@yahoo.it>
> Cc: buildroot at uclibc.org
> Inviato: Mercoled? 27 febbraio 2008, 16:52:03
> Oggetto: Re: [Buildroot] Problem with iperf
>
>
> NWFPE is the floating point emulator.
>
> 00000002 is a floating point divide-by-zero.
>
> try another version of iperf maybe?
> report this problem to the iperf maintainer?
> -Rex
>
>
> On 2/27/08, Nicola Salvemini <nicolasalvemini@yahoo.it> wrote:
> >
> > Hi all,
> >
> > I have a ARM arm926t (it's a little-endian) target platform and I use
> > buildroot to cross-compile applications.
> > I include iperf in the package selection for the target and the build
> > phase go to the end without problems, but when I try to use iperf on the
> > target, I take an exception:
> >
> > NWFPE: iperf[770] takes exception 00000002 at c00288f0 from 400f4580
> > NWFPE: iperf[770] takes exception 00000002 at c00288f0 from 400f4580
> > NWFPE: iperf[770] takes exception 00000002 at c00288f0 from 400f4580
> >
> > Could you please give me an idea to resolve the problem?
> > Thanks in advance,
> >
> >
> > Nicola.
> >
> >
> >
> >
> >
> > ___________________________________
> > L'email della prossima generazione? Puoi averla con la nuova Yahoo!
> > Mail: http://it.docs.yahoo.com/nowyoucan.html<http://it.docs..yahoo.com/nowyoucan.html>
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at uclibc.org
> > http://busybox.net/mailman/listinfo/buildroot
> >
>
>
>
> ------------------------------
> ------------------------------
> L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail<http://us.rd.yahoo.com/mail/it/taglines/hotmail/nowyoucan/nextgen/*http://it.docs.yahoo.com/nowyoucan.html>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080228/8df3feb6/attachment.htm
next parent reply other threads:[~2008-02-28 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <337959.75035.qm@web23402.mail.ird.yahoo.com>
2008-02-28 15:33 ` Rex Ashbaugh [this message]
2008-02-29 15:07 [Buildroot] Problem with iperf Nicola Salvemini
-- strict thread matches above, loose matches on Subject: below --
2008-02-28 16:28 Nicola Salvemini
2008-02-28 17:21 ` Rex Ashbaugh
2008-02-27 15:32 Nicola Salvemini
2008-02-27 15:52 ` Rex Ashbaugh
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=6311fe0b0802280733q17996f0n14e5cedade44df78@mail.gmail.com \
--to=rexa@xeratech.com \
--cc=buildroot@busybox.net \
/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