From: Thomas Schlichter <thomas.schlichter@web.de>
To: Stephen Lord <lord@sgi.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Compile warnings due to missing __inline__ in fs/xfs/xfs_log.h
Date: Wed, 18 Dec 2002 01:05:40 +0100 [thread overview]
Message-ID: <200212180105.41255.thomas.schlichter@web.de> (raw)
In-Reply-To: <1040147719.1368.424.camel@localhost.localdomain>
OK, thanks for that info, now I understand...
So I think I better take the warnings ;-)
Thomas
Am Dienstag, 17. Dezember 2002 18:55 schrieb Stephen Lord:
> On Tue, 2002-12-17 at 10:01, Thomas Schlichter wrote:
> > As the __inline__ directive in front of the _lsn_cmp function is not used
> > with the gcc version 2.95.x, compile-warnings result from many files
> > including this header-file.
>
> The reason inline is turned off for this compiler version is that it
> generates bad code when inlining this code. So you can have a quiet
> compile, or bad code.
>
> Steve
prev parent reply other threads:[~2002-12-17 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 16:01 Compile warnings due to missing __inline__ in fs/xfs/xfs_log.h Thomas Schlichter
2002-12-17 17:55 ` Stephen Lord
2002-12-18 0:05 ` Thomas Schlichter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212180105.41255.thomas.schlichter@web.de \
--to=thomas.schlichter@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox