From: "H. Peter Anvin" <hpa@zytor.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Jie Zhang <jzhang.linux@gmail.com>, Adrian Bunk <bunk@kernel.org>,
bryan.wu@analog.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] blackfin: "extern inline" -> "static inline"
Date: Wed, 24 Oct 2007 20:06:14 -0700 [thread overview]
Message-ID: <47200826.1060801@zytor.com> (raw)
In-Reply-To: <8bd0f97a0710242000h7b6c97e7ia3f461c69b7d5de5@mail.gmail.com>
Mike Frysinger wrote:
> On 10/24/07, Jie Zhang <jzhang.linux@gmail.com> wrote:
>> On 10/25/07, Adrian Bunk <bunk@kernel.org> wrote:
>>> "extern inline" will have different semantics with gcc 4.3.
>>>
>>> Signed-off-by: Adrian Bunk <bunk@kernel.org>
>>>
>>> --- a/include/asm-blackfin/string.h
>>> +++ b/include/asm-blackfin/string.h
>>> @@ -4,7 +4,7 @@
>>> #ifdef __KERNEL__ /* only set these up for kernel code */
>>>
>>> #define __HAVE_ARCH_STRCPY
>>> -extern inline char *strcpy(char *dest, const char *src)
>>> +static inline char *strcpy(char *dest, const char *src)
>>> {
>>> char *xdest = dest;
>>> char temp = 0;
>> What if we compile it with gcc 4.1?
>
> we'll have to either use the gcc attributes to force old inline
> behavior or use the gcc flag to force it
We should probably have an extern_inline define then, assuming this is a
function that does exist in a linkable version already -- otherwise
"static inline" is correct.
-hpa
next prev parent reply other threads:[~2007-10-25 3:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:26 [2.6 patch] blackfin: "extern inline" -> "static inline" Adrian Bunk
2007-10-25 2:47 ` Jie Zhang
2007-10-25 3:00 ` Mike Frysinger
2007-10-25 3:06 ` H. Peter Anvin [this message]
2007-10-25 3:17 ` Mike Frysinger
2007-10-25 15:05 ` Adrian Bunk
2007-10-25 16:16 ` Mike Frysinger
2007-10-25 16:53 ` Adrian Bunk
2007-10-25 20:07 ` Mike Frysinger
2007-10-25 20:18 ` Adrian Bunk
2007-10-25 20:20 ` Mike Frysinger
2007-10-25 20:28 ` H. Peter Anvin
2007-10-25 20:45 ` Mike Frysinger
2007-10-25 20:53 ` H. Peter Anvin
2007-10-25 20:47 ` Adrian Bunk
2007-10-25 20:54 ` H. Peter Anvin
2007-10-25 20:46 ` Adrian Bunk
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=47200826.1060801@zytor.com \
--to=hpa@zytor.com \
--cc=bryan.wu@analog.com \
--cc=bunk@kernel.org \
--cc=jzhang.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.