Message-ID: <004701c3236c$b04afb50$0100a8c0@acp42g>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: <djgpp-workers AT delorie DOT com>, "Richard Dawe" <rich AT phekda DOT freeserve DOT co DOT uk>
References: <000b01c31df6$5e2e9fa0$0100a8c0 AT acp42g> <3ED10D06 DOT 8BC7AA6B AT phekda DOT freeserve DOT co DOT uk>
Subject: Re: LIBC patch for GCC 3.3 - part  #1
Date: Mon, 26 May 2003 19:53:40 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Reply-To: djgpp-workers AT delorie DOT com

> > Below are the first part of a set of patches that allow the CVS LIBC to
be
> > built with GCC 3.3. This one patched the gcc option files and fixes some
> > type issues.
> [snip]
>
> Thanks.
>
> I've committed the changes to strtod, strtold with one change: the
variables
> are unsigned, so I used 'ULL' instead of 'LL'.
Thanks for fixing the unsigned and comitting it.

> I don't like the -fno-strict-aliasing change. If we commit it now, it may
not
> get removed when we do a release. I'd much prefer that the two places that
> suffer from the aliasing warning ("type punning" IIRC) are fixed. I don't
> think it will be that hard. (See the gcc info docs about type punning and
how
> we can use a union.)
There is allot more than the two places than I gave as examples.

Let me have a another try on this one later this week.

Andrew