X-pop3-spooler:	POP3MAIL 2.1.0 b 3 961213 -bs-
Delivered-To:	pcg AT goof DOT com
To:	Marc Lehmann <pcg AT goof DOT com>
Cc:	Jan Gyselinck <JAN DOT GYSELINCK AT student DOT kuleuven DOT ac DOT be>,
	beastium <beastium-list AT Desk DOT nl>
Subject:	Re: Problem with pgcc....
References:	<19980317152303 DOT 02815 AT cerebro DOT laendle> <Pine DOT WNT DOT 3 DOT 96 DOT 980318150049 DOT -109495A-100000 AT IPV26083 DOT cc DOT kuleuven DOT ac DOT be> <19980318231115 DOT 38975 AT cerebro DOT laendle>
Mime-Version:	1.0 (generated by tm-edit 7.108)
From:	Florian Weimer <fw AT cygnus DOT stuttgart DOT netsurf DOT de>
Date:	19 Mar 1998 07:56:52 +0100
In-Reply-To:	Marc Lehmann's message of "Wed, 18 Mar 1998 23:11:15 +0100"
Message-ID:	<m3hg4v5ft7.fsf@cygnus.stuttgart.netsurf.de>
X-Mailer:	Gnus v5.5/XEmacs 20.4 - "Emerald"
Sender:	Marc Lehmann <pcg AT goof DOT com>
Status:	RO
X-Status:	A
Lines:	19

Marc Lehmann <pcg AT goof DOT com> writes:

> On Wed, Mar 18, 1998 at 03:14:57PM +0100, Jan Gyselinck wrote:
> > > 
> > > I don't care for broken programs. If programs don't compile anymore, it's by
> > > 99.999% a bug in these programs. Better fix the programs rather than
> > > kludging your compiler.
> > Or not-documented behavior, maybe?  Programs are there to help the user,
> > isn't it? :p
> 
> well, linus says it isn't documented ;) actually, it is ambiguos. But that
> one problem (ioperm) is neither a documentation problem nor a compiler bug,
> and it was fixed long ago in 2.1.x

You have to be careful here. ;-) A quick fix suggested by Alan Cox
didn't work at all: gcc 2.8.0 optimized away a reference to a volatile
memory location, which is clearly a bug...

fw

- Raw text -