public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stephen L Moshier <steve@moshier.net>
To: Zack Weinberg <zack@codesourcery.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Java floating-point mess
Date: Fri, 05 Apr 2002 11:01:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0204051247440.18828-100000@moshier.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0204050943100.18396-100000@moshier.net>


Here are the external functions that real.o seems to reference:

  mode_class
  mode_bitsize

  warning
  extra_warnings
  fancy_abort
  _hex_value
  _sch_istable

The reference to mode_class could just be deleted because it occurs
only in a sanity test that is probably not vitally important.

mode_bitsize is used to determine the width of types such as SFmode
etc.  I think that this code originally just tested for the
machine_mode enum, and it could revert to that.  (If you want
DFmode to be 32 bits wide, or some such, you are already in
deep trouble.)  Alternatively the two functions that use mode_bitsize,
REAL_VALUE_FROM_INT and REAL_VALUE_FROM_UNSIGNED_INT, might be removed to
a separate source file if you don't need them in java.

The other external references, fancy_abort, etc., do not look like they
are specific to the back end though I didn't check to see if they
are present in java.   _hex_value and _sch_istable were not used and
could be eliminated by reverting to an earlier version of the code.


  reply	other threads:[~2002-04-05 18:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05  8:00 Stephen L Moshier
2002-04-05 11:01 ` Stephen L Moshier [this message]
2002-04-08 10:20 ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08 13:15 Robert Dewar
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=Pine.LNX.4.33.0204051247440.18828-100000@moshier.net \
    --to=steve@moshier.net \
    --cc=gcc@gcc.gnu.org \
    --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).