X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Message-ID: <3FE5DB66.8000108@phekda.gotadsl.co.uk>
Date: Sun, 21 Dec 2003 17:41:58 +0000
From: Richard Dawe <rich AT phekda DOT gotadsl DOT co DOT uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031031
X-Accept-Language: en, de, fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: isnanf et al
References: <14f DOT 2822ab47 DOT 2d15f1a0 AT aol DOT com> <3FE5AF50 DOT 7020603 AT phekda DOT gotadsl DOT co DOT uk> <3405-Sun21Dec2003183453+0200-eliz AT elta DOT co DOT il>
In-Reply-To: <3405-Sun21Dec2003183453+0200-eliz@elta.co.il>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Eli Zaretskii wrote:
>>Date: Sun, 21 Dec 2003 14:33:52 +0000
>>From: Richard Dawe <rich AT phekda DOT gotadsl DOT co DOT uk>
>>
>>>The fixes would entail modifying the 24 files in libm v204 that were 
>>>mentioned in the email.  My suggestion is to revert to the sources for 
>>>those files in libm v203.
>>
>>That would break the build with gcc 3.3.x (and 3.2.x?). Those changes 
>>were made, so that DJGPP 2.04 could be built with gcc 3.3.x (and 3.2.x?).
> 
> 
> Can you remind what kind of problems were those?  I think we should
> look for a solution that fixes them without triggering this new
> problem.

They were errors about type-punning breaking strict aliasing (search the 
gcc info docs for -fstrict-aliasing and you should find a section about 
it). Using a union is the only valid way of doing type-punning, but it 
seems that using it was the wrong solution. By using the union I guess 
you're telling the compiler "I know what I'm doing", like with typecasts.

Bye, Rich =]

-- 
Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ]

"You can't evaluate a man by logic alone."
   -- McCoy, "I, Mudd", Star Trek