| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: linux/fs/xfs/xfs_log.h:_lsn_cmp not declared __inline__ with gcc 2.95 |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Fri, 14 Feb 2003 12:26:15 -0800 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1045253892.463.1183.camel@xxxxxxxxxxxxxxxxxxxx> |
| References: | <20030214201059.GA25006@xxxxxxxx> <1045253892.463.1183.camel@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
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? For me, it *seems* to work... if it's not working, what can I expect to see? Am I silently experincing corruption as I type this? :( > Hopefully the compiler will be fixed in the future and the inline > can be restored. Anyone else tested this? --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: linux/fs/xfs/xfs_log.h:_lsn_cmp not declared __inline__ with gcc 2.95, Steve Lord |
|---|---|
| Next by Date: | Re: linux/fs/xfs/xfs_log.h:_lsn_cmp not declared __inline__ with gcc 2.95, Steve Lord |
| Previous by Thread: | Re: linux/fs/xfs/xfs_log.h:_lsn_cmp not declared __inline__ with gcc 2.95, Steve Lord |
| Next by Thread: | Re: linux/fs/xfs/xfs_log.h:_lsn_cmp not declared __inline__ with gcc 2.95, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |