linux-kernel - Please be aware that __always_inline doesn't mean "always inline"!

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 for Android: free password hash cracker in your pocket

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

Message-ID: <50638DCC.5040506@att.net>
Date:	Wed, 26 Sep 2012 18:20:44 -0500
From:	Daniel Santos <danielfsantos@....net>
To:	LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
	torvalds@...ux-foundation.org
Subject: Please be aware that __always_inline doesn't mean "always inline"!

I've noticed that there's a lot of misperception about the meaning of
the __always_inline, or more specifically,
__attribute__((always_inline)), which does not actually cause the
function to always be inlined.  Rather, it *allows* gcc to inline the
function, even when compiling without optimizations.  Here is the
description of the attribute from gcc's docs
(http://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/Function-Attributes.html)

always_inline
Generally, functions are not inlined unless optimization is specified.
For functions declared inline, this attribute inlines the function even
if no optimization level was specified.

This would even appear to imply that such functions aren't even marked
as "inline" (something I wasn't aware of until today).  The only
mechanism I'm currently aware of to force gcc to inline a function is
the flatten attribute (see https://lkml.org/lkml/2012/9/25/643) which
works backwards, you declare it on the calling function, and it forces
gcc to inline all functions (marked as inline) that it calls.

Daniel
--
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/