From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19767 invoked by alias); 27 Sep 2007 00:42:17 -0000 Received: (qmail 19758 invoked by uid 22791); 27 Sep 2007 00:42:16 -0000 X-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,TW_DW,TW_FL X-Spam-Check-By: sourceware.org Received: from mga03.intel.com (HELO mga03.intel.com) (143.182.124.21) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 27 Sep 2007 00:42:14 +0000 Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 26 Sep 2007 17:42:12 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.21,200,1188802800"; d="scan'208";a="287466497" Received: from fmsmsx334.amr.corp.intel.com ([132.233.42.1]) by azsmga001.ch.intel.com with ESMTP; 26 Sep 2007 17:42:12 -0700 Received: from scsmsx411.amr.corp.intel.com ([10.3.90.30]) by fmsmsx334.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 26 Sep 2007 17:42:12 -0700 Received: from scsmsx415.amr.corp.intel.com ([10.3.90.34]) by scsmsx411.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 26 Sep 2007 17:42:11 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: Disappearing return value Date: Thu, 27 Sep 2007 15:29:00 -0000 Message-ID: <16D5B9AB904B0B46B22A27002EE3A8C8F38A61@scsmsx415.amr.corp.intel.com> In-Reply-To: <46FAE35B.10604@us.ibm.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Disappearing return value Thread-Index: AcgAkGEMbDgl9Rt2Q/SZiUmFfJTPrgADXolA References: <46FAE35B.10604@us.ibm.com> From: "Stone, Joshua I" To: "Mike Mason" , "systemTAP" X-OriginalArrivalTime: 27 Sep 2007 00:42:11.0927 (UTC) FILETIME=[3DF42670:01C8009F] X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00727.txt.bz2 Mike Mason wrote: > nfs_check_flags() looks like a candidate for inlining during > optimization, but then I'd expect an error indicating no return probe > could be set. Is this a known problem? I confirmed this on two of my machines, one RHEL5 (2.6.18-8.1.1.el5 i686) and one F7 (2.6.22.5-76.fc7 x86_64). A function pointer to nfs_check_flags is saved in nfs_file_operations, so it can't be completely inlined. I suppose that it could still be inlined at the call in nfs_file_open, but turning on more verbose output doesn't seem to indicate that. parsed 'nfs_check_flags' -> func 'nfs_check_flags' pattern 'nfs' matches module 'nfs' focused on module 'nfs =3D [0x1d52174-0x1d7ebc1, bias 0x0] file /lib/modules/2.6.18-8.1.1.el5/kernel/fs/nfs/nfs.ko ELF machine i?86 (code 3) pattern 'nfs_check_flags' matches function 'nfs_check_flags' selected function nfs_check_flags probe nfs_check_flags@?:-1 module=3Dnfs reloc=3D.text section=3D.text pc=3D0x1d56258 literal_stmt_for_return: finding return value for nfs_check_flags(fs/nfs/file.c) dwarf_builder releasing dwflpp semantic error: function has no return value: identifier '$return' at :1:66 Bizarre... Josh