From: Hans-Bernhard Broeker <broeker AT acp3bf DOT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: BUG !
Date: 15 Feb 2000 13:12:09 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 23
Message-ID: <88bjb9$qid$1@nets3.rz.RWTH-Aachen.DE>
References: <001a01bf777c$ecbca7e0$3ca812d4 AT miguel>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 950620329 27213 137.226.32.75 (15 Feb 2000 13:12:09 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 15 Feb 2000 13:12:09 GMT
User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586))
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Miguel Tetembua Campino Vale <mtcv AT camoes DOT rnl DOT ist DOT utl DOT pt> wrote:

>   I don't know if is a DJGPP bug or GCC bug.

Neither of them, strictly spoken. The gcc folks had to change the
behaviour for some cases of extended inline assembly, and the code
you're compiling is now incompatible with current GCC versions. The
code will have to be fixed.

>   I try to compile "v2tk/lsck073s.zip" with gcc v2.95.x and some error
> in file "lsck073/src/wsock/vxd.c" line 37, --->   :"%eax", "%edx");

You clipped the whole error message text away. You shouldn't have done
that, as it makes it unnecessarily hard to see what might have gone
wrong.  'Some error' is just too vague a description, in the general
case.

But even so, I think it's clearly guessable that it must have been the
'fixed or forbidden register was spilled' error message. There's an
article in the Web-based GCC FAQ (below www.gnu.org) about it.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.