xfs
[Top] [All Lists]

Re: linux/fs/xfs/xfs_log.h:_lsn_cmp not declared __inline__ with gcc 2.

To: Steve Lord <lord@xxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>
Subject: Re: linux/fs/xfs/xfs_log.h:_lsn_cmp not declared __inline__ with gcc 2.95
From: Seth Mos <knuffie@xxxxxxxxx>
Date: Sat, 15 Feb 2003 19:25:43 +0100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <1045254513.466.1185.camel@xxxxxxxxxxxxxxxxxxxx>
References: <20030214202615.GB25088@xxxxxxxx> <20030214201059.GA25006@xxxxxxxx> <1045253892.463.1183.camel@xxxxxxxxxxxxxxxxxxxx> <20030214202615.GB25088@xxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
At 14:28 14-2-2003 -0600, Steve Lord wrote:
On Fri, 2003-02-14 at 14:26, Chris Wedgwood wrote:
> On Fri, Feb 14, 2003 at 02:18:12PM -0600, Steve Lord wrote:
>
> > The way I remember it - 2.95 generated bad code here.
>
> Which gcc-2.95?

Well, thats the problem, there is no way to divine more about
the compiler than 2.95, so the code cannot tell. I think the
problem came out as recovery failures, or maybe a cpu loop
somewhere, I really cannot remember anymore.

Zombie proccesses. Mainly loopdiloops. Process stuck in D state. A very early version of 2.96 also had this IIRC.

2.95.2 was the main crulpit. 2.95.3 and above are safe.

Cheers

--
Seth
It might just be your lucky day, if you only knew.


<Prev in Thread] Current Thread [Next in Thread>