From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Koning <pkoning@xedia.com>
To: manfred@s-direktnet.de
Cc: law@cygnus.com, rms@gnu.org, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: New problems with gcc-2.8.0 based code - NOW FIXED! 
Date: Tue, 30 Dec 1997 13:17:00 -0000
Message-id: <9712301904.AA09186@kona.>
References: <199712291737.SAA07160@saturn.s-direktnet.de> <26093.883419397@hurl.cygnus.com> <199712301444.PAA00543@saturn.s-direktnet.de>
X-SW-Source: 1997-12/msg01251.html

GCC 2.7.2.1 had a bug that showed up in some backends, and EGCS
exposed it with more backends, where asm statements that should have
been treated as unmovable were actually moved.  (Spefically, those
with no output arguments; the documentation quite rightly says that
those are always treated as if they were marked "volatile" even when
not so marked.)

That bug was fixed in egcs just a few weeks ago.  If gcc 2.8.x doesn't
have the corresponding fix, that could account for the problem.  As I
recall from the earlier discussion, one symptom of the bug was that
Linux would crash or otherwise misbehave, but only if you turned on
"enough" optimization.

The fix was only a few lines, you might try the experiment of applying
it to gcc 2.8 if the relevant module is reasonably similar.

	paul