linux-kernel - Re: Status of CONFIG_FORCED

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: <4655C8B8.7020205@linux.intel.com>
Date:	Thu, 24 May 2007 10:17:44 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Adrian Bunk <bunk@...sta.de>
CC:	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Rob Landley <rob@...dley.net>, linux-kernel@...r.kernel.org
Subject: Re: Status of CONFIG_FORCED_INLINING?

Adrian Bunk wrote:
> On Thu, May 24, 2007 at 06:29:39PM +0200, Jan Engelhardt wrote:
>> On May 23 2007 23:22, Adrian Bunk wrote:
>>> And we need only two different inline levels (__always_inline and
>>> "let the compiler decide"), not three (__always_inline, inline and
>>> "let the compiler decide").
>> "inline" is "let the compiler decide". If it is not, then it is "let the
>> compiler decide, based on my bias that I think it should be inlined".
> 
> Wrong.
> "static" is "let the compiler decide".
> 
and "inline" is "give the compiler a suggestion". Not more than that.
-
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/