From: dewar@gnat.com (Robert Dewar)
To: dewar@gnat.com, tromey@redhat.com
Cc: aph@cambridge.redhat.com, gcc@gcc.gnu.org, java@gcc.gnu.org,
zack@codesourcery.com
Subject: Re: Java floating-point mess
Date: Mon, 08 Apr 2002 13:15:00 -0000 [thread overview]
Message-ID: <20020408200158.84BD0F28EA@nile.gnat.com> (raw)
<<The front end is required to do these computations in some contexts,
namely compile-time constants. This is a concern to us, but it isn't
immediately pressing. We already violate the spec with respect to
compile-time constants in several ways.
>>
Sure, of course I understand that, but these computations should be done
using simulated IEEE arithmetic rather than host arithmetic.
next reply other threads:[~2002-04-08 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 13:15 Robert Dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-05 8:00 Stephen L Moshier
2002-04-05 11:01 ` Stephen L Moshier
2002-04-08 10:20 ` Tom Tromey
2002-04-05 6:25 Robert Dewar
2002-04-08 7:58 ` Tom Tromey
2002-04-04 6:11 Robert Dewar
2002-04-04 13:00 ` Zack Weinberg
2002-04-05 4:49 ` Andrew Haley
2002-04-04 3:56 Zack Weinberg
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=20020408200158.84BD0F28EA@nile.gnat.com \
--to=dewar@gnat.com \
--cc=aph@cambridge.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=tromey@redhat.com \
--cc=zack@codesourcery.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).