From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-49485-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 15306 invoked by alias); 4 Apr 2002 11:56:20 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 15287 invoked from network); 4 Apr 2002 11:56:16 -0000
Received: from unknown (HELO nile.gnat.com) (205.232.38.5)
  by sources.redhat.com with SMTP; 4 Apr 2002 11:56:16 -0000
Received: by nile.gnat.com (Postfix, from userid 338)
	id 04DBBF28C0; Thu,  4 Apr 2002 06:56:15 -0500 (EST)
To: gcc@gcc.gnu.org, zack@codesourcery.com
Subject: Re: Java floating-point mess
Message-Id: <20020404115615.04DBBF28C0@nile.gnat.com>
Date: Thu, 04 Apr 2002 06:11:00 -0000
From: dewar@gnat.com (Robert Dewar)
X-SW-Source: 2002-04/txt/msg00137.txt.bz2

<<The Java front end has a number of places that assume not only that
the host and target floating point formats are identical, but that
both are IEEE.  I've tried to get rid of them, but run afoul of its
not being possible to link real.o into gcjh -- it wants to drag in
most of the back end.
>>

Presumably the complaint is about assuming that the host fpt format is
IEEE, the target fpt format presumably MUST be IEEE, since this is required
by Java, no?