From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82586 invoked by alias); 2 May 2019 07:06:08 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 82578 invoked by uid 89); 2 May 2019 07:06:08 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (209.51.188.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 02 May 2019 07:06:06 +0000 Received: from fencepost.gnu.org ([2001:470:142:3::e]:38147) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hM5n6-0001w2-JJ; Thu, 02 May 2019 03:06:01 -0400 Received: from [176.12.229.109] (port=37645 helo=[10.208.206.146]) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1hM5mq-0005DN-BU; Thu, 02 May 2019 03:05:46 -0400 Date: Thu, 02 May 2019 07:06:00 -0000 User-Agent: K-9 Mail for Android In-Reply-To: <20190501195113.69aea752@f30-4.lan> References: <83wojaovbp.fsf@gnu.org> <077aee8c-7bef-bad6-a6a1-e69f116cc18b@simark.ca> <20190501195113.69aea752@f30-4.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: The 'cold' function attribute and GDB To: gdb-patches@sourceware.org,Kevin Buettner ,Simon Marchi From: Eli Zaretskii Message-ID: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-IsSubscribed: yes X-SW-Source: 2019-05/txt/msg00031.txt.bz2 On May 2, 2019 5:51:13 AM GMT+03:00, Kevin Buettner wro= te: > On Wed, 1 May 2019 16:17:04 -0400 > Simon Marchi wrote: >=20=20 > > In an ideal world, if gcc generates two separate ranges > > of instruction for this function (the hot path and the cold path), > it should describe > > it as two ranges in the entry for print_vectorlike. If so, it > should be described with > > a DW_AT_ranges attribute. >=20 > Yes, this is exactly right. I do see in the DWARF info that print_vectorlike has 2 address ranges: its = DW_AT_ranges attribute specifies a value which is shown as a list of 2 rang= es in the "objdump -WR" output. So where do I go from here? What to check next? Thanks.