Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752677AbZAKWqY (ORCPT ); Sun, 11 Jan 2009 17:46:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751795AbZAKWqM (ORCPT ); Sun, 11 Jan 2009 17:46:12 -0500 Received: from turing-police.cc.vt.edu ([128.173.14.107]:33331 "EHLO turing-police.cc.vt.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751458AbZAKWqK (ORCPT ); Sun, 11 Jan 2009 17:46:10 -0500 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: "H. Peter Anvin" Cc: Ingo Molnar , jim owens , Linus Torvalds , Chris Mason , Peter Zijlstra , Steven Rostedt , paulmck@linux.vnet.ibm.com, Gregory Haskins , Matthew Wilcox , Andi Kleen , Andrew Morton , Linux Kernel Mailing List , linux-fsdevel , linux-btrfs , Thomas Gleixner , Nick Piggin , Peter Morreale , Sven Dietrich Subject: Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact In-Reply-To: Your message of "Fri, 09 Jan 2009 08:34:57 PST." <49677CB1.3030701@zytor.com> From: Valdis.Kletnieks@vt.edu References: <20090108141808.GC11629@elte.hu> <1231426014.11687.456.camel@twins> <1231434515.14304.27.camel@think.oraclecorp.com> <20090108183306.GA22916@elte.hu> <496648C7.5050700@zytor.com> <20090109130057.GA31845@elte.hu> <49675920.4050205@hp.com> <20090109153508.GA4671@elte.hu> <49677CB1.3030701@zytor.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1231713934_4078P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 11 Jan 2009 17:45:34 -0500 Message-ID: <100584.1231713934@turing-police.cc.vt.edu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1198 Lines: 32 --==_Exmh_1231713934_4078P Content-Type: text/plain; charset=us-ascii On Fri, 09 Jan 2009 08:34:57 PST, "H. Peter Anvin" said: > A lot of noise is being made about the naming of the levels (and I > personally believe we should have a different annotation for "inline > unconditionally for correctness" and "inline unconditionally for > performance", as a documentation issue), but those are the four we get. I know we use __builtin_return_address() in several places, and several other places we introspect the stack and need to find the right frame entry. Are there any other places that need to be inlined for correctness? --==_Exmh_1231713934_4078P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Exmh version 2.5 07/13/2001 iD8DBQFJanaOcC3lWbTT17ARAhshAJ9EuXy6AsnovZqJBsb30GqNfgRW6QCgvxMc 9XcAbNlET4hJRlR00Jexkjk= =CaEV -----END PGP SIGNATURE----- --==_Exmh_1231713934_4078P-- -- 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/