From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 125221 invoked by alias); 3 May 2017 11:23:30 -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 124956 invoked by uid 89); 3 May 2017 11:23:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy= X-HELO: mail-wm0-f49.google.com Received: from mail-wm0-f49.google.com (HELO mail-wm0-f49.google.com) (74.125.82.49) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 03 May 2017 11:23:27 +0000 Received: by mail-wm0-f49.google.com with SMTP id w64so143299617wma.0 for ; Wed, 03 May 2017 04:23:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=uWk6PNT9S5RWdSJoT5PcJX3eJ1Lx4MtRA73w/nCgBdU=; b=GRtrF6wLw5sQIs59KctwGzvFNC+jh61eF3CQZwTecnFWZk3R85fazwLJWPOdFr9cvz iU6mNHc6uTsJ3nCNgQIWPyqiBpF2cgE8lQkc8BxRZYlAN5CDFvki3l0wyjzgSkFaiAXq EK5D4qAX9fJ0xqJsMA4DVmHBL81/IYJr9XOLYMd4NuT8TiJb7ycOVRMWAtBI29I8STgd 1KrAg0kU0kjE5Ok9t5f4WmbNa1GHfuAQH8yPJHxnitdDSKGkYsgjyHDlDRVn9htV53TE SVpAyZfHe4ay+LH/3ZG+OKir12M8plCo1LTIbkWVqOfL/TYSbXVT6rB8dFt8btcKJFo8 i0UQ== X-Gm-Message-State: AODbwcC2C3g6Gt2CuCrwisPKYbXSEiuGBftT0yfUwBcgN0oUkA8LYIXw Iz8mhJIkDqX17d8ZS90NAQ== X-Received: by 10.28.9.20 with SMTP id 20mr485179wmj.117.1493810608172; Wed, 03 May 2017 04:23:28 -0700 (PDT) Received: from [192.168.0.102] ([37.189.166.198]) by smtp.gmail.com with ESMTPSA id 136sm4502676wmx.25.2017.05.03.04.23.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 May 2017 04:23:27 -0700 (PDT) Subject: Re: [PATCH 8/11] Add FRV_MAX_REGISTER_SIZE To: Alan Hayward References: <3B3BD949-1C9D-44FF-AB6A-03091ECA49D0@arm.com> <867f2rw9br.fsf@gmail.com> <22BD364F-A9A9-4E21-BC47-96A320760640@arm.com> <86d1bqba87.fsf@gmail.com> Cc: Yao Qi , "gdb-patches@sourceware.org" , nd From: Pedro Alves Message-ID: Date: Wed, 03 May 2017 11:23:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-05/txt/msg00046.txt.bz2 On 05/03/2017 11:56 AM, Alan Hayward wrote: >> BTW, note that gdbserver has an equivalent function, called >> "supply_register_zeroed". > +/* Supply register REGNUM with zeroed value to REGCACHE. This is not the same > + as calling raw_supply with NULL (which will set the state to > + unavailable). */ > + > +void > +regcache::raw_supply_zero (int regnum) A very minor detail, but I'd prefer it if gdb and gdbserver agreed on terminology. Should we call this one "zeroed" too, or rename gdbserver's to "zero"? Thanks, Pedro Alves