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
| ||
|
Date: Wed, 23 May 2007 14:28:56 -0700 From: Roland Dreier <rdreier@...co.com> To: Adrian Bunk <bunk@...sta.de> Cc: Arjan van de Ven <arjan@...ux.intel.com>, Rob Landley <rob@...dley.net>, linux-kernel@...r.kernel.org Subject: Re: Status of CONFIG_FORCED_INLINING? > - every static function in a header file must be __always_inline Why? Why does it matter whether a function is defined in a .h file or a .c file? Can't the compiler decide better than we can whether something should be inlined or not? Your argument seems to imply that we should never use the inline keyword at all. - R. - 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/
Powered by blists - more mailing lists