linux-kernel - Re: can someone explain "inline" once and for all?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <84144f020701190501x5d1efb49u87dc9537bfe1e791@mail.gmail.com>
Date:	Fri, 19 Jan 2007 15:01:44 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	"Linux kernel mailing list" <linux-kernel@...r.kernel.org>
Subject: Re: can someone explain "inline" once and for all?

On 1/19/07, Robert P. J. Day <rpjday@...dspring.com> wrote:
> is there a simple explanation for how to *properly* define inline
> routines in the kernel?  and maybe this can be added to the
> CodingStyle guide (he mused, wistfully).

AFAIK __always_inline is the only reliable way to force inlining where
it matters for correctness (for example, when playing tricks with
__builtin_return_address like we do in the slab).

Anything else is just a hint to the compiler that might be ignored if
the optimizer thinks it knows better.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/