public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: FLOATING-POINT CONSISTENCY, -FFLOAT-STORE, AND X86
Date: Sat, 19 Dec 1998 14:03:00 -0000	[thread overview]
Message-ID: <rzqsoebokmi.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <19981219001659.L2289@cerebro.laendle>

>>>>> "Marc" == Marc Lehmann <pcg@goof.com> writes:

 >> What's the guarantee that crt0 sets up extended precision on
 >> whichever systems are of interest?

 Marc> I have no idea. Do _you_ have one?

No, or I wouldn't have asked.  AFAIR the startup settings of the FPU
changed at some stage in the past, though.

 >> Is it currently consistent across all the x86 platforms we run on?

 Marc> Definitely not. But does that mean we should break linux-libm
 Marc> (for example) because solaris behavuour wasn't consistent
 Marc> before(?).

Of course not.  I need libm to work; that's why I keep asking the
question.  I presume that glibc would need to conform on another
platform that did define this.

 Marc> How about implementing the __setfpucw functionality as found on
 Marc> linux? Creating a library (-lrdble) should be trivial then.

I don't have the information, expertise or interest in that.  I called
__setfpucw, but I'm not even sure it works across Linuxes.  I'd do
newlib and cygwin32 as well, given appropriate doc and a way of
figuring out that they're in use; AFAIR they seem to have the facility
but don't say how to drive it.  I'd expect people with an interest to
contribute the (presumably trivial) additions.

  reply	other threads:[~1998-12-19 14:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-17  1:43 N8TM
1998-12-17 12:35 ` Marc Lehmann
1998-12-18 12:14   ` Dave Love
1998-12-18 14:25     ` Gerald Pfeifer
1998-12-19 13:50       ` Dave Love
1998-12-18 18:37     ` Marc Lehmann
1998-12-19 14:03       ` Dave Love [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-12-22 13:30 Toon Moene
1998-12-22 11:07 John Wehle
1998-12-21 23:30 N8TM
1998-12-19 15:17 Geert Bosch
1998-12-20  8:09 ` Toon Moene
1998-12-22  4:17 ` Dave Love
1998-12-19 14:26 N8TM
1998-12-19 14:23 N8TM
1998-12-20 13:51 ` Marc Lehmann
1998-12-20 13:52   ` Marc Lehmann
1998-12-19 13:00 N8TM
1998-12-19  9:05 N8TM
1998-12-19 12:39 ` Toon Moene
1998-12-19 14:42   ` Dave Love
1998-12-18 23:07 N8TM
1998-12-19 13:39 ` Marc Lehmann
1998-12-18 21:58 N8TM
1998-12-18 22:36 ` Richard Henderson
1998-12-19 13:41   ` Marc Lehmann
1998-12-16  6:10 N8TM
1998-12-15  0:05 N8TM
1998-12-15 10:01 ` Joe Buck
1998-12-13  6:19 Stephen L Moshier
1998-12-13 10:49 ` Craig Burley
1998-12-13 15:18   ` Stephen L Moshier
1998-12-14  8:49     ` Craig Burley
1998-12-14  9:25       ` Joe Buck
1998-12-14 14:30         ` Edward Jason Riedy
1998-12-15  0:04         ` Craig Burley
1998-12-03  6:34 N8TM
1998-12-04 15:23 ` Craig Burley

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=rzqsoebokmi.fsf@djlvig.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=egcs@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).