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: Fri, 19 Jan 2007 06:56:54 -0500 (EST) From: "Robert P. J. Day" <rpjday@...dspring.com> To: Linux kernel mailing list <linux-kernel@...r.kernel.org> Subject: can someone explain "inline" once and for all? apologies if this is an inappropriately trivial question but this has been bugging me for a while. what is the deal with "inline"? first, there appear to be three possible ways of specifying an inline routine in the kernel source: $ grep -r "static inline " . $ grep -r "static __inline__ " . $ grep -r "static __inline " . i vaguely recall that this has something to do with a distinction between C99 inline and gcc inline and trying to avoid a clash between the two, but i'm not going to put any money on that. but the confusion probably explains why so many people insist on creating new macros to represent inline: $ grep -r "#define.*inline" . 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). rdau - 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