From: Mike Stump <mrs@apple.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: mark@codesourcery.com, steby@enea.se, gcc@gcc.gnu.org
Subject: Re: GCC floating point usage
Date: Tue, 15 Oct 2002 19:04:00 -0000 [thread overview]
Message-ID: <0638B6F4-E09D-11D6-8136-000393941EE6@apple.com> (raw)
In-Reply-To: <200210152337.g9FNbkG07955@desire.geoffk.org>
On Tuesday, October 15, 2002, at 04:37 PM, Geoff Keating wrote:
> OK, that's a good description. It's clear, easily understood, and has
> a bunch of consequences I bet you haven't thought of yet :-).
>
> For instance, consider a program that uses setjmp in one file, which
> contains no use of FP but uses routines from another file that call
> longjmp and do use FP.
I believe that case has been thought of. The thing that is marked as
FP or not, is a task. A task that is not marked as FP cannot by
definition call a routine that is in a task that does use FP. No
problem here.
A routine that is compiled with no-implicit-fp is valid to use in a
no-FP task, provided there is no explicit fp in it. A routine that
isn't compiled with this flag isn't valid to use in a non-FP task.
> Note that this doesn't apply to "most code"; assuming vxworks defaults
> to -msoft-float,
It does not. It multilibs softfloat. On softfloat system, the entire
implicit-fp issue it a non-issue, so we don't care about those. The
only case we care about is by definition on hardfloat systems, when the
context switcher may, or may not save/restore the FP regs.
next prev parent reply other threads:[~2002-10-16 0:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 9:59 Stefan Bylund
2002-10-14 10:16 ` David Edelsohn
2002-10-14 10:25 ` Zack Weinberg
2002-10-14 10:55 ` Dale Johannesen
2002-10-14 22:22 ` Mark Mitchell
2002-10-15 15:35 ` Geoff Keating
2002-10-15 16:10 ` Mark Mitchell
2002-10-15 17:20 ` Geoff Keating
2002-10-15 18:09 ` Mark Mitchell
2002-10-16 7:40 ` Joel Sherrill
2002-10-15 19:04 ` Mike Stump [this message]
2002-10-16 12:06 ` Mark Mitchell
2002-10-16 13:35 ` Geoff Keating
2002-10-16 14:29 ` Mark Mitchell
2002-10-16 14:56 ` Michael Matz
2002-10-16 15:03 ` Mark Mitchell
2002-10-16 15:27 ` David Edelsohn
2002-10-16 15:36 ` Mark Mitchell
2002-10-16 16:35 ` Zack Weinberg
2002-10-16 16:36 ` Mark Mitchell
2002-10-16 16:46 ` David Edelsohn
2002-10-17 8:37 ` Paul Koning
2002-10-16 17:57 ` Mike Stump
2002-10-17 4:12 ` Mike Stump
2002-10-16 13:43 ` Richard Henderson
2002-10-16 14:35 ` Mark Mitchell
2002-10-16 14:56 ` Joel Sherrill
2002-10-16 16:38 ` Richard Henderson
2002-10-16 16:53 ` Zack Weinberg
2002-10-16 17:52 ` Michael Matz
2002-10-16 22:50 ` Richard Henderson
2002-10-21 12:21 ` Jeff Law
2002-10-16 17:29 ` Mike Stump
2002-10-17 2:19 ` Richard Henderson
2002-10-15 17:19 ` Mike Stump
2002-10-15 18:41 ` Zack Weinberg
2002-10-16 1:48 ` Fergus Henderson
2002-10-14 10:37 ` Stefan Bylund
2002-10-14 11:28 ` Mike Stump
2002-10-14 12:39 ` Joel Sherrill
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=0638B6F4-E09D-11D6-8136-000393941EE6@apple.com \
--to=mrs@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
--cc=mark@codesourcery.com \
--cc=steby@enea.se \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).