linux-kernel - Re: Status of CONFIG_FORCED

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]

Message-ID: <20070524171019.GA4470@stusta.de>
Date:	Thu, 24 May 2007 19:10:19 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Roland Dreier <rdreier@...co.com>
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?

On Wed, May 23, 2007 at 02:28:56PM -0700, Roland Dreier wrote:
>  > - 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.

A function only belongs into a header file if we always want it inlined, 
otherwise it belongs into a C file.

>  - R.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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