From: Paul Mackerras <paulus@cs.anu.edu.au>
To: paubert@iram.es
Cc: dje@watson.ibm.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Current egcs, binutils and kernel (fwd)
Date: Sat, 24 Apr 1999 22:35:04 +1000 [thread overview]
Message-ID: <199904241235.WAA25761@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.HPP.3.96.990420223651.20020P-100000@gra-ux1.iram.es> (message from Gabriel Paubert on Tue, 20 Apr 1999 22:43:24 +0200 (METDST))
Gabriel Paubert <paubert@iram.es> wrote:
> to correctly implement this. And then I've noticed just after that people
> do more work than necessary in the cvt_df and cvt_fd routines: floating
> point loads and stores never affect or depend on the FPSCR contents, so
Arrghl, you're right. I had thought you could get overflows or other
errors being signalled, that's why I had the fpscr load/save in there,
but it appears from the manual that I was wrong.
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-04-24 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Geert.Uytterhoeven@cs.kuleuven.ac.be>
1999-04-20 11:39 ` Current egcs, binutils and kernel (fwd) Geert Uytterhoeven
1999-04-20 17:05 ` David Edelsohn
1999-04-20 20:43 ` Gabriel Paubert
1999-04-20 21:14 ` David Edelsohn
1999-04-20 21:26 ` Gabriel Paubert
1999-04-24 12:35 ` Paul Mackerras [this message]
1999-04-20 17:45 ` Gabriel Paubert
1999-04-20 18:29 ` Gary Thomas
[not found] <Pine.LNX.4.10.9904201339320.26859-100000@mercator.cs.kuleu ven.ac.be>
1999-04-20 14:49 ` Franz Sirl
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=199904241235.WAA25761@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=dje@watson.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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).