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: <200705241414.20258.rob@landley.net>
Date:	Thu, 24 May 2007 14:14:19 -0400
From:	Rob Landley <rob@...dley.net>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	Roland Dreier <rdreier@...co.com>, Adrian Bunk <bunk@...sta.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Status of CONFIG_FORCED_INLINING?

On Thursday 24 May 2007 1:47 pm, Arjan van de Ven wrote:
> Rob Landley wrote:
> > If the compiler can emit a warning "inline insanely large", we can use 
that to 
> > fix it.  But a warning is not the same as silently doing something other 
than 
> > what we told it to do.
> 
> It's not silent! that's what "inline" without the force is for!
> Once you force it you shut the warning up!!!!

So presumably, a debug option could #define __always_inline to just "inline" 
in order to get warning messages to look at?

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