Message-ID: <3eb94933$0$79348$cc7c7865@news.luth.se>
From: Martin Str|mberg <ams AT speedy DOT ludd DOT luth DOT se>
Subject: Re: SIGILL 386 (illegal opcode)
Newsgroups: comp.os.msdos.djgpp
References: <b8oqgi$1s2b$1 AT hq DOT mark-itt DOT ru> <3eb08a5a$0$79355$cc7c7865 AT news DOT luth DOT se> <b8qpgj$2tb4$1 AT hq DOT mark-itt DOT ru>
User-Agent: tin/1.4.6-20020816 ("Aerials") (UNIX) (NetBSD/1.6Q (alpha))
Date: 07 May 2003 17:58:12 GMT
Lines: 25
NNTP-Posting-Host: speedy.ludd.luth.se
X-Trace: 1052330292 news.luth.se 79348 130.240.16.13
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

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.


Right,

						MartinS