From: Ralf Baechle <ralf@oss.sgi.com>
To: Dominic Sweetman <dom@algor.co.uk>
Cc: Jay Carlson <nop@nop.com>,
mad-dev@lists.mars.org, Carlo Agostini <carlo.agostini@yacme.com>,
linux-mips@oss.sgi.com
Subject: Re: Problems compiling . soft-float
Date: Tue, 26 Feb 2002 13:27:12 +0100 [thread overview]
Message-ID: <20020226132711.A18296@dea.linux-mips.net> (raw)
In-Reply-To: <15483.27029.29266.976139@gladsmuir.algor.co.uk>; from dom@algor.co.uk on Tue, Feb 26, 2002 at 10:55:17AM +0000
On Tue, Feb 26, 2002 at 10:55:17AM +0000, Dominic Sweetman wrote:
> Incremental changes to the ABI are pretty bad news. Isn't it
> avoidable in this case?
>
> It seems to me that soft-float programs are either carefully
> controlled test cases, or used as part of a 100% soft-float system.
>
> In the first case the programmer had better take care, and in the
> second the kernel should have been changed to kill any program with an
> FP op-code.
Experience shows that people will use every opportunity to shot themselfes
into their foot ...
Even a soft-fp system may still have the in-kernel emulator, so be able to
execute both soft-fp and hard-fp binaries correctly. But it won't be able
to support a mix of both nor would the kernel know that an application is
just mixing hard and soft fp.
Ralf
prev parent reply other threads:[~2002-02-26 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 7:19 Problems compiling . soft-float Carlo Agostini
2002-02-25 12:25 ` Ralf Baechle
2002-02-26 4:47 ` Jay Carlson
2002-02-26 5:02 ` Ralf Baechle
2002-02-26 5:10 ` Daniel Jacobowitz
2002-02-26 5:23 ` Jay Carlson
2002-02-26 5:28 ` Jay Carlson
2002-02-26 5:51 ` Daniel Jacobowitz
2002-02-26 12:59 ` Maciej W. Rozycki
2002-02-26 12:59 ` Maciej W. Rozycki
2002-02-26 12:59 ` Maciej W. Rozycki
2002-02-26 10:55 ` Dominic Sweetman
2002-02-26 12:27 ` Ralf Baechle [this message]
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=20020226132711.A18296@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=carlo.agostini@yacme.com \
--cc=dom@algor.co.uk \
--cc=linux-mips@oss.sgi.com \
--cc=mad-dev@lists.mars.org \
--cc=nop@nop.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.