X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient:	djgpp-workers AT delorie DOT com
Date:	Sat, 01 Aug 2009 10:36:57 +0300
From:	Eli Zaretskii <eliz AT gnu DOT org>
Subject:	Re: Some patches to DJGPP v2.04 (GCC-4.4.1 related)
In-reply-to:	<4A73E13E.3050700@iki.fi>
X-012-Sender:	halo1 AT inter DOT net DOT il
To:	djgpp-workers AT delorie DOT com
Message-id:	<83skgcouhy.fsf@gnu.org>
References:	<4A73E13E DOT 3050700 AT iki DOT fi>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Sat, 01 Aug 2009 09:31:26 +0300
> From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
> 
> At first fighting with strict aliasing violation warnings from emu387.cc
> could be rather big work. Perhaps it is easier to tell GCC not to
> complain. The option -fno-strict-aliasing is available beginning from
> gcc-2.8.0 if I remember correctly. So unless somebody terribly
> wants to build DJGPP v2.04pre with really ancient gcc-2.7.2.1, I guess
> it should be OK to apply the patch. Am I right?

Yes, I think so.  DJ?

> There also was type punning related warning from src/compat/mntent/mntent.c.
> Does the related patch seem OK?

Yes.

> After that (+ telling gcc to stay silent about conflicting parameters
> for some builtin functions in libm and using command line option -m32
> for building host tools) all seems to build OK using gcc-4.4.1 under
> Fedora 11 x86_64.

Shouldn't a cross-gcc for DJGPP use -m32 by default?

Thanks.

- Raw text -