From: Rob Landley <rob@landley.net>
To: Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: Status of CONFIG_FORCED_INLINING?
Date: Thu, 24 May 2007 14:14:19 -0400
User-Agent: KMail/1.9.1
Cc: Roland Dreier <rdreier@cisco.com>, Adrian Bunk <bunk@stusta.de>,
       linux-kernel@vger.kernel.org
References: <200705231510.52932.rob@landley.net> <200705241347.43727.rob@landley.net> <4655CFB8.7060708@linux.intel.com>
In-Reply-To: <4655CFB8.7060708@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705241414.20258.rob@landley.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 764
Lines: 20

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/