This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: undefined errors for inline function

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: Xi Ruoyao <ryxi at stu dot xidian dot edu dot cn>
Cc: vijay nag <vijunag at gmail dot com>, "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
Date: Mon, 30 Jan 2017 10:29:34 +0000
Subject: Re: undefined errors for inline function
Authentication-results: sourceware.org; auth=none
References: <CAKhyrx8d3Ccs9tCBO+ESYZDC4VDdVFu8JtTV+ks0FgcbH9pfNA@mail.gmail.com> <1485768853.8710.10.camel@stu.xidian.edu.cn>

On 30 January 2017 at 09:34, Xi Ruoyao wrote:
> The C99 Standard (ISO/IEC 9899:1999 6.7.4) says:
>
>     Function specifiers shall be used *only* in the declaration of
>     an identifier for a function.
>
> In linker.c, we use the function specifier ``inline" in a
> *definition*. It's illegal.

I'm pretty sure that's not true. See the example slightly later in
6.7.4 that uses inline on function definitions.

A function definition is also a declaration, so it's allowed to have
the inline specifier.

The text you quoted means you can't put inline on declarations of
variables or types, only functions.

References:
- RE: undefined errors for inline function
  - From: vijay nag
- Re: undefined errors for inline function
  - From: Xi Ruoyao

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]