From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: bartv@cygnus.co.uk
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: Ecos Port to PPC509/PPC555
Date: Tue, 28 Sep 1999 08:02:00 -0000 [thread overview]
Message-ID: <37F0D88A.EF0DCD5E@cygnus.co.uk> (raw)
In-Reply-To: <199909281459.PAA09627@sheesh.cygnus.co.uk>
Bart Veer wrote:
>
> >>>>> "Jifl" == Jonathan Larmour <jlarmour@cygnus.co.uk> writes:
> Jifl> But you can't rely on FP exceptions being generated - they
> Jifl> don't for normal code, so I don't believe this is a viable
> Jifl> option unless I've misunderstood you.
>
> On some architectures including the PPC (if I remember correctly), it
> is possible to disable the floating point unit. The first operation
> that attempts to access the floating point unit, even if it is just to
> access a floating point register, will cause a hardware exception.
> This is separate from normal floating point exceptions such as
> overflow.
Oops yes. I did misunderstand you :-). For what its worth, MIPS and x86 have
this as well IIRC.
Jifl
--
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK. Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
my brains kept falling out." || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/ These opinions are all my own fault
next prev parent reply other threads:[~1999-09-28 8:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-21 12:32 [ECOS] " Ramana
1999-09-22 2:01 ` Sergei Organov
1999-09-23 8:16 ` [ECOS] " Bart Veer
1999-09-24 4:39 ` Sergei Organov
1999-09-24 8:52 ` Jonathan Larmour
1999-09-24 10:34 ` Sergei Organov
1999-09-27 11:54 ` Bart Veer
1999-09-27 17:36 ` Jonathan Larmour
1999-09-28 4:23 ` Sergei Organov
1999-09-28 7:42 ` Jonathan Larmour
1999-09-28 8:00 ` Bart Veer
1999-09-28 8:02 ` Jonathan Larmour [this message]
1999-09-28 4:19 ` Sergei Organov
1999-09-28 8:08 ` Jonathan Larmour
1999-09-28 11:03 ` Bart Veer
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=37F0D88A.EF0DCD5E@cygnus.co.uk \
--to=jlarmour@cygnus.co.uk \
--cc=bartv@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.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 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).