X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient:	djgpp-workers AT delorie DOT com
Message-ID:	<4A7522DE.2020509@iki.fi>
Date:	Sun, 02 Aug 2009 08:23:42 +0300
From:	Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent:	Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Thunderbird/3.0b2
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Some patches to DJGPP v2.04 (GCC-4.4.1 related)
References:	<4A73E13E DOT 3050700 AT iki DOT fi> <83skgcouhy DOT fsf AT gnu DOT org> <200908020128 DOT n721S4rc001722 AT envy DOT delorie DOT com>
In-Reply-To:	<200908020128.n721S4rc001722@envy.delorie.com>
Reply-To:	djgpp-workers AT delorie DOT com

02.08.2009 04:28, DJ Delorie kirjoitti:
>> Yes, I think so.  DJ?
>
> Ok with me, although if we can avoid aliasing problems by coding I'd
> prefer that.  At some point, strict aliasing may be the only option.

I completely agree. However looking how hast things advance now, one
could expect it after many years from now, perhaps if or when one
decides to deprecate and remove GCC command line option
-fno-strict-aliasing.

There is one more workaround available: one can use optimization
levels which does not involve strict aliasing related optimization
or no optimizations at all. Currently that would be -O1 or -O0.

>
>> Shouldn't a cross-gcc for DJGPP use -m32 by default?
>
> He said *host* tools.  He's building on x86_64, although I don't see
> why it matters what host tools you're using; I originally cross-built
> djgpp on an SGI IRIX.
>

64 bit dxegen3 compiled on x86_64 Linux does not work and crashes. I remember
we discussed that sometimes earlier and as I remember the reason was
BFD related. The workaround for Linux x86_64 is to use -m32.

There is however a question whether dxegen3 will work when compiled on
completely different 64 bit (non x86_64 processor). I do not have any
such for testing.

Andris

- Raw text -