From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@netx4.com>
Cc: Wolfgang Denk <wd@denx.de>,
brian.neidig@ni.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Cross-compiling standard utilities for 860
Date: Wed, 26 Jan 2000 17:50:51 +0100 [thread overview]
Message-ID: <200001261650.RAA01770@denx.local.net> (raw)
In-Reply-To: Your message of "Wed, 26 Jan 2000 11:01:25 EST." <388F1A55.D62E35B4@netx4.com>
In message <388F1A55.D62E35B4@netx4.com> Dan Malek wrote:
>
> You have to be careful here. If you choose to use the in-line
> floating point software, you must use it for all applications
> because the libraries are built to do this as well. You can't
> mix programs that use the kernel FPU emulation and also in-line
> software floating-point. The kernel works out of the floating
> point register area in the TSS, while the software float assigns
> real processor registers (and other memory locations) to contain
> the floating-point values.
I am aware that I cannot mix this WITHIN ONE application, for
instance compiling the app with soft-float and linking against a
library that uses the kernel FPU emulation.
Are there really problems when running soft-float only and FPU emu
only applications on the same machine? I did not expect any...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Anyone who isn't confused here doesn't really know what's going on.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-01-26 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <388F1A55.D62E35B4@netx4.com>
2000-01-26 16:50 ` Wolfgang Denk [this message]
2000-01-26 17:04 Cross-compiling standard utilities for 860 Matthew R Wette
-- strict thread matches above, loose matches on Subject: below --
2000-01-26 2:45 brian.neidig
2000-01-26 7:20 ` Wolfgang Denk
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=200001261650.RAA01770@denx.local.net \
--to=wd@denx.de \
--cc=brian.neidig@ni.com \
--cc=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).