From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 48853 invoked by alias); 26 Oct 2018 12:13:45 -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 48803 invoked by uid 89); 26 Oct 2018 12:13:43 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=HContent-Transfer-Encoding:8bit X-HELO: smtp.eurecom.fr Received: from smtp.eurecom.fr (HELO smtp.eurecom.fr) (193.55.113.210) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 26 Oct 2018 12:13:41 +0000 Received: from waha.eurecom.fr (HELO smtps.eurecom.fr) ([10.3.2.236]) by drago1i.eurecom.fr with ESMTP; 26 Oct 2018 14:13:38 +0200 Received: from [10.0.3.38] (unknown [193.55.114.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtps.eurecom.fr (Postfix) with ESMTPSA id CD7BA23A; Fri, 26 Oct 2018 14:13:37 +0200 (CEST) Subject: Re: [PATCH] ARM: Do not use FP reg when on AAPCS To: Kevin Buettner , gdb-patches@sourceware.org Cc: Marius Muench , Pedro Alves References: <20181023101649.23d4af8b@pinnacle.lan> <406505df-13d3-08de-ad86-fc38131eb4b9@redhat.com> <15364ecd-125d-7196-8e83-e6db60127005@eurecom.fr> <20181025133418.68b513e1@pinnacle.lan> From: Marius Muench Openpgp: preference=signencrypt Message-ID: <7772abce-b035-8a82-67da-1bd948f6c759@eurecom.fr> Date: Fri, 26 Oct 2018 12:13:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20181025133418.68b513e1@pinnacle.lan> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2018-10/txt/msg00620.txt.bz2 Thanks! I don't have push permissions, as it is my first contribution to this project. I can't find any documentation what to do in this case, scraping the ML, I see three possible strategies: (1) One of you push on my behalf. (2) I send a new (clean) version of this patch, which gets pushed on my behalf. (3) Push permissions are set up. What's your preferred strategy here? Thanks a lot, Marius On 10/25/18 10:34 PM, Kevin Buettner wrote: > On Wed, 24 Oct 2018 21:37:07 +0200 > Marius Muench wrote: > >> Fair enough, updated version below. >> >> gdb/ChangeLog: >> 2018-10-24 Marius Muench >> >> * arm-tdep.c (arm_scan_prologue): Don't dereference FP reg >> when on AAPCS. > > Looks good to me. > > You can commit / push this now... > > Kevin >