linux-kernel - Re: optimizing out inline functions

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]

Date:	Wed, 28 May 2008 22:54:47 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Steve French" <smfrench@...il.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: optimizing out inline functions

On Wed, May 28, 2008 at 10:51 PM, Steve French <smfrench@...il.com> wrote:
> Is one or the other style (with or without #define of empty function)
> preferred?  Does the compiler optimize both #else clauses out
> properly?  sparse and checkpatch seem to take either

Both are optimized out but empty function is preferred for type checking.
--
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/