From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12548 invoked by alias); 30 Nov 2018 20:10:17 -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 12409 invoked by uid 89); 30 Nov 2018 20:10:16 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=blacklist, whitelist X-HELO: gateway32.websitewelcome.com Received: from gateway32.websitewelcome.com (HELO gateway32.websitewelcome.com) (192.185.145.111) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 30 Nov 2018 20:10:15 +0000 Received: from cm12.websitewelcome.com (cm12.websitewelcome.com [100.42.49.8]) by gateway32.websitewelcome.com (Postfix) with ESMTP id AB3D27CAC0 for ; Fri, 30 Nov 2018 14:10:13 -0600 (CST) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id Sp77gMjU4SjJASp77gjgXV; Fri, 30 Nov 2018 14:10:13 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=YgRfnqOudjeB+inZuzdQiwyNv/rQdOUiYoxmlZt+JQ0=; b=fQEWb1Jd3cec+k0zyslfyaEi6W Q78n6mRVl3g46lcaB+pU9nb2+WNTygFq2ZpAJoaX9wj3axJ+3jGvn2wN2NsmKg0PoM2xafK5cj1ya HGpix/Lm5X5sve//Ee8p9wjMa; Received: from 97-122-190-66.hlrn.qwest.net ([97.122.190.66]:58506 helo=pokyo) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gSp77-0027KI-Cd; Fri, 30 Nov 2018 14:10:13 -0600 From: Tom Tromey To: Alan Hayward Cc: Simon Marchi , "gdb-patches\@sourceware.org" , nd Subject: Re: [PATCH 1/2] Allow function prologues to have multiple repeating lines References: <20181024090427.22721-1-alan.hayward@arm.com> <0BDE5F6A-06E9-4246-A1C6-1F8E0F22C983@arm.com> Date: Fri, 30 Nov 2018 20:10:00 -0000 In-Reply-To: <0BDE5F6A-06E9-4246-A1C6-1F8E0F22C983@arm.com> (Alan Hayward's message of "Mon, 5 Nov 2018 16:04:35 +0000") Message-ID: <87efb2mimz.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2018-11/txt/msg00585.txt.bz2 >>>>> "Alan" =3D=3D Alan Hayward writes: [...] Alan> So, I don=E2=80=99t think it=E2=80=99s possible to tell apart the fir= st example with the final Alan> example. What does the DWARF look like? Ideally I think gdb would just rely on the DWARF to mark the end of the prologue. However, of course that can't always be done -- but I would much rather have a blacklist of bad compilers than the current approach of a whitelist of good ones; and I'm wondering if that is achievable at all. Maybe doing this well would mean exposing a bit more info from the DWARF to gdb's line table -- but that seems totally fine. Maybe I'm really not understanding the problem, feel free to say so :) But I'd like to understand better; my own forays into this area haven't turned out so well. thanks, Tom