| 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
| ||
|
Message-ID: <20061201173647.GB10549@colo.lackof.org> Date: Fri, 1 Dec 2006 10:36:47 -0700 From: Grant Grundler <grundler@...isc-linux.org> To: Adrian Bunk <bunk@...sta.de> Cc: Grant Grundler <grundler@...isc-linux.org>, Andrew Morton <akpm@...l.org>, matthew@....cx, kyle@...isc-linux.org, parisc-linux@...isc-linux.org, linux-kernel@...r.kernel.org Subject: Re: [2.6 patch] parisc: "extern inline" -> "static inline" (fwd) On Fri, Dec 01, 2006 at 05:54:27PM +0100, Adrian Bunk wrote: > If you read John David Anglin's email, you'll note that if you take the > address you need this function provided somewhere. Let me turn that around. Which of the "extern inline" functions are we taking the address? The parisc kernel wouldn't (shouldn't) link if that were true. > Which of the functions my patch changes also have a global function > provided within the kernel? > > If none, "extern inline" didn't make any sense. I expect none. ... > Currently, "inline" is defined to be always_inline, and > __always_inline is for cases that produce non-compiling or non-working > (opposed to only suboptimal) code. Ok. Sounds like "extern inline" is the same as __always_inline. Has gcc community confirmed "gcc -Wmissing-prototypes" behavior is really correct with respect to "extern inline"? If so, I'm ok with changing "extern inline" to __always_inline. thanks, grant - 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