From: Andris Pavenis <pavenis AT latnet DOT lv>
To: djgpp-workers AT delorie DOT com, Martin Str|mberg <ams AT ludd DOT luth DOT se>
Subject: Re: (fwd) Re: SIGILL 386 (illegal opcode)
Date: Wed, 7 May 2003 23:55:15 +0300
User-Agent: KMail/1.5.1
References: <200305071759 DOT h47HxQte028947 AT speedy DOT ludd DOT luth DOT se>
In-Reply-To: <200305071759.h47HxQte028947@speedy.ludd.luth.se>
Cc: "Alexei K." <kzua AT kzua DOT udm DOT ru>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305072355.16047.pavenis@latnet.lv>
Reply-To: djgpp-workers AT delorie DOT com

On Wednesday 07 May 2003 20:59, Martin Str|mberg wrote:
>
> It seems that I'm having really bad luck posting this to the
> lists. Here I go again.
>
> Alexei K. <kzua AT kzua DOT udm DOT ru> wrote:
> : "Martin Str|mberg" <ams AT speedy DOT ludd DOT luth DOT se>:
> : news:3eb08a5a$0$79355$cc7c7865 AT news DOT luth DOT se...
> :
> :> If you get SIGILL we want more information. Like what program and
> :> source? Command line? Result?
> :
> : My project works fine with 386 CPU, if it compiles by DJGPP gpp 2.952.
> : I have just recompiled my project by DJGPP gpp 3.2.2
> : (with -m386 option enabled) and program has failed only on 386 PC.
> : I deeply use STL. Was libstdxx.a library compiled for 386 CPU?
>
> Your problem indicate it was not.
>
> It should work on 386s.
>
> I hope the GCC maintainer corrects this for the following releases of
> GCC.

xaddl can be found in inline assembler in atomicity.h. Therefore specifying 
-march=i386 or -m386 doesn't help much. It's also in gcc-3.2.3, and there 
will be no more  releases from gcc-3.2 branch.

Problems with atomicity.h were recently discussed in gcc mailing lists. Don't 
expect enything done with gcc-3.2.X. Let's see how it will be in gcc-3.3 when 
it will be released (don't ask dates, I don't know)

Andris