On Wed, Aug 14, 2013 at 05:37:41PM -0400, beh...@converseincode.com wrote: > From: Mark Charlebois <charl...@gmail.com> > > With compilers which follow the C99 standard (like modern versions of gcc and > clang), "extern inline" does the wrong thing (emits code for an externally > linkable version of the inline function). In this case using the gnu_inline > attribute makes inline do the right thing on gcc and on clang. > > Signed-off-by: Mark Charlebois <charl...@gmail.com> > Signed-off-by: Behan Webster <beh...@converseincode.com> > --- > arch/arm/include/asm/ftrace.h | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/arm/include/asm/ftrace.h b/arch/arm/include/asm/ftrace.h > index f89515a..fb7fdc4 100644 > --- a/arch/arm/include/asm/ftrace.h > +++ b/arch/arm/include/asm/ftrace.h > @@ -45,7 +45,8 @@ void *return_address(unsigned int); > > #else > > -extern inline void *return_address(unsigned int level) > +extern inline __attribute__((gnu_inline)) > +void *return_address(unsigned int level)
Well, that should be static inline, not extern inline in any case. Does clang work if that's static inline? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
