VAX Ultrix bootstrap failure with gcc-2.96

[John David Anglin]

Forwarded message:
>From dave Thu May 25 22:20:54 EDT 2000
Subject: Re: VAX Ultrix bootstrap failure with gcc-2.96
To: zack@wolery.cumb.org (Zack Weinberg)
Date: Thu, 25 May 2000 22:20:54 -0400 (EDT)
From: "John David Anglin" <dave@hiauly1>
Cc: gcc-patches@gcc.gnu.org, egcs-bugs@sourceware.cygnus.com
In-Reply-To: <20000525183119.T3314@wolery.cumb.org> from "Zack Weinberg" at May 25, 2000 06:31:19 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 907       

> It did catch some real bugs, so I'm not complaining.  What are the
> $ in identifier messages complaining about?  It's probably another
> warning that should be turned off in system headers, or something like
> that.

The $ in identifier messages are complaining about lines like

#if     defined(__GFLOAT) || CC$gfloat

which occur in limits.h (syslimits.h) and math.h in the gcc include
directory.  The identifier CC$gfloat is something the VAX ANSI C
compiler defines.  Probably, this should be nuked when the includes
are fixed.  It obviously isn't needed in the gcc include directory.

Another small related issue is that gcc should define __GFLOAT
in addition to GFLOAT when the -mg option is used.  I have edited
my specs file to do this.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)


-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)