X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient:	djgpp-workers AT delorie DOT com
X-Authenticated:	#27081556
X-Provags-ID:	V01U2FsdGVkX19uhEcCWo1u7B+beryyRcIfzRlyL7vT+npF1RfV9J
	+AFVA2AICfoaMS
From:	Juan Manuel Guerrero <juan DOT guerrero AT gmx DOT de>
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Difficulties compiling emu387.cc with gcc 4.3.0
Date:	Tue, 10 Jun 2008 09:13:00 +0200
User-Agent:	KMail/1.9.5
References:	<200806092058 DOT 05925 DOT juan DOT guerrero AT gmx DOT de> <484D91C2 DOT 1050004 AT iki DOT fi>
In-Reply-To:	<484D91C2.1050004@iki.fi>
MIME-Version:	1.0
Message-Id:	<200806100913.00759.juan.guerrero@gmx.de>
X-Y-GMX-Trusted:	0
Reply-To:	djgpp-workers AT delorie DOT com

Am Montag, 9. Juni 2008 22:25 schrieben Sie:
> > I have tried to compile today's CVS sources and I have run into a problem.
> > I am using gcc 4.3.0 and bnu217br2.  The sources can only be compiled if
> > Andris' patches to emu387.cc and ieeefp.h are applied (see 
> ><http://www.delorie.com/archives/browse.cgi?p=djgpp-workers/2008/05/01/08:49:44>
> >
> Not committed because I don't know whether it is correct. Perhaps 
> somebody who know emu387.cc
> better could say more

The fix seems logical/right comparing the "offending" lines with somilar code
lines, but that is not really a good argument.  On the other hand, I think the
original author of the code will not come to our help, so some day a decision
must be taken.  In the worst case, if it the patch is applied,  the code is brocken
again or brocken in a different way.


[snip]
> > the compilation of emu387.cc fails with the following error message:
> >
> >
> > ./makemake.exe
> > makemake: scanning libemu for makefiles
> > C:/djgpp/bin/make.exe -f makefile.sub
> > C:/djgpp/bin/make.exe -C src 
> > gcc -MD -O2 -mtune=i586 -march=i386 -Wall  -Wcast-qual -Werror   -Wpointer-arith -Wshadow  -Wwrite-strings -Wundef -Wcast-align -Wsign-compare -nostdinc -iquote . -isystem ../../../include -DGAS_MAJOR=2 -DGAS_MINOR=17 -DGAS_MINORMINOR=0 -c -fno-exceptions emu387.cc
> > cc1plus.exe: warnings being treated as errors
> > emu387.cc: In function 'void fsqrt()':
> > emu387.cc:2366: error: likely type-punning may break strict-aliasing rules: object '*{unknown}' of main type 'long int' is referenced at or around emu387.cc:2366 and may be aliased to object 'result' of main type 'long long unsigned int' which is referenced at or around emu387.cc:2357.
> > emu387.cc:2371: error: likely type-punning may break strict-aliasing rules: object '*{unknown}' of main type 'unsigned int' is referenced at or around emu387.cc:2371 and may be aliased to object 'val' of main type 'long long unsigned int' which is referenced at or around emu387.cc:2356.
> > make.exe[3]: *** [emu387.o] Error 1
> > make.exe[2]: *** [all_subs] Error 2
> > make.exe[1]: *** [all] Error 2
> > make.exe: *** [subs] Error 2
> >
> >  
> Compiles for me with GCC-4.3.1 when my attached patch is being used.

Using your new patch it still fails in the same way as told before.  I will wait
until you make available gcc 4.3.1 and test again to see if my installation is
brocken.


Regards,
Juan M. Guerrero

- Raw text -