From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129769 invoked by alias); 13 Dec 2016 11:48:27 -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 129680 invoked by uid 89); 13 Dec 2016 11:48:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: =?ISO-8859-1?Q?No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy==e5=b0=a7, H*MI:sk:alan.ha, H*f:D4757157.1649A, H*i:sk:alan.ha?= X-HELO: mail-wm0-f65.google.com Received: from mail-wm0-f65.google.com (HELO mail-wm0-f65.google.com) (74.125.82.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 13 Dec 2016 11:48:03 +0000 Received: by mail-wm0-f65.google.com with SMTP id g23so17866865wme.1 for ; Tue, 13 Dec 2016 03:48:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=AjJiO3oElgciQjLDWw4S6+PUclkkwrJvXbpS+PdY9d8=; b=FDacB4kDaxhr0CpJ5z/s/dPXNDNj50G9klZEV/BDpYRqGbr1cvENmRTxRK4B7IaB77 R1UZSxluJvejCfjL72vLmVGdPsPICS/rbZWTqlGP7Osz3ruFa8ZthVTI4vtLhDwNMImq xIrjRj6+DxAHY53ad7ex6g2jbY7xh5pXYuQTbDtd8hKhWfeKbKJtKfhkI8D67RRHERmD e246A2TqZq5oGZak3Le00YD2ozyuiW6JAhkvCBC88S3i4VdyxZshtQZ05Xh8pxbtfAJM DVBtUVetAdkfcxA6abfCyBh84ZRNFkPzCvs4HO2H8poLnbTL34KM0X4UxjeHSSJv3hc2 x+jg== X-Gm-Message-State: AKaTC03XAq+oHeQ6+W/IjhN8Ugb3LdqKLufMtAa1BBN1ErjBX2sk9gbhk6T9ahFUqEJLtQ== X-Received: by 10.28.170.202 with SMTP id t193mr2148833wme.10.1481629681581; Tue, 13 Dec 2016 03:48:01 -0800 (PST) Received: from E107787-LIN (gcc1-power7.osuosl.org. [140.211.15.137]) by smtp.gmail.com with ESMTPSA id d85sm2222952wmd.17.2016.12.13.03.47.59 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Tue, 13 Dec 2016 03:48:00 -0800 (PST) Date: Tue, 13 Dec 2016 11:48:00 -0000 From: Yao Qi To: Alan Hayward Cc: "gdb-patches@sourceware.org" Subject: Re: [PATCH 1/8] AARCH64 SVE: Increse max register sizes Message-ID: <20161213114742.GF25542@E107787-LIN> References: <20161212181032.GC25542@E107787-LIN> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2016-12/txt/msg00284.txt.bz2 On 16-12-13 10:05:49, Alan Hayward wrote: > I’ve just noticed I forgot to add a changelog for all of my patches. > Apologies - I’ll add them for any V2 versions (or happy to repost all of > them again with changelogs if required). ChangeLog is not needed for V1. > > On 12/12/2016 18:10, "Yao Qi" wrote: > > >On 16-12-05 12:26:24, Alan Hayward wrote: > >> This is part of a series adding AARCH64 SVE support to gdb and > >>gdbserver. > >> > >> In SVE the maximum size of a variable-length vector register is 256 > >>bytes, > >> four > >> times the current maximum size currently supported in gdb. This patch > >> increases > >> the max register size and max gdbserver buffer size accordingly. > > > >Joel expressed the willingness that we should make MAX_REGISTER_SIZE > >gdbarch specific last time when it was changed from 32 to 64. > >https://sourceware.org/ml/gdb-patches/2010-09/msg00245.html > >I think we should make MAX_REGISTER_SIZE gdbarch specific, or stop > >using it at all. > > I’m happy to do this if that’s what people want. I avoided doing it > because I > didn’t want to subtly break something and it’s going to be quite a large > change - > I might submit it a set of patches by itself. > You can start from changing amd64-tdep.c and frame.c, which are interesting to most of people here. It shouldn't take long to finish the patch, and post it to get feedback quickly. If people agree/like the change, then you can move on changing the rest in the same way. -- Yao (齐尧)