public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org, parisc-linux@parisc-linux.org,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: [parisc-linux] [2.6 patch] parisc: "extern inline" -> "static inline"
Date: Wed, 2 Nov 2005 06:53:48 -0700	[thread overview]
Message-ID: <20051102135348.GI23749@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0511021448010.8013@yvahk01.tjqt.qr>

On Wed, Nov 02, 2005 at 02:48:42PM +0100, Jan Engelhardt wrote:
> 
> >> "extern inline" doesn't make much sense.
> 
> But GNU's ld is said to be smart enough to handle this like the 
> developerwants "extern AND inline". I did not try, though.

I think you're gravely confused.  Look at the assembly that gcc spits
out for extern inline functions.  The linker never even gets to see the
function.  Try it out, it'll be good practice for you.

  reply	other threads:[~2005-11-02 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30  0:03 [2.6 patch] parisc: "extern inline" -> "static inline" Adrian Bunk
2005-10-30 15:22 ` [parisc-linux] " Matthew Wilcox
2005-10-30 15:56   ` Adrian Bunk
2005-10-30 16:42     ` [parisc-linux] [2.6 patch] parisc: "extern inline" -> "static John David Anglin
2005-10-30 17:14       ` Adrian Bunk
2005-11-02 13:48   ` [parisc-linux] [2.6 patch] parisc: "extern inline" -> "static inline" Jan Engelhardt
2005-11-02 13:53     ` Matthew Wilcox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-19 17:19 Adrian Bunk
2006-08-21 14:42 ` [parisc-linux] " Kyle McMartin

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=20051102135348.GI23749@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=bunk@stusta.de \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parisc-linux@parisc-linux.org \
    /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