From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 58688 invoked by alias); 1 Feb 2017 12:45:04 -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 58591 invoked by uid 89); 1 Feb 2017 12:45:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=17-01-27, 170127, HX-Received:Wed, HX-Received:Feb X-HELO: mail-wm0-f67.google.com Received: from mail-wm0-f67.google.com (HELO mail-wm0-f67.google.com) (74.125.82.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 01 Feb 2017 12:45:01 +0000 Received: by mail-wm0-f67.google.com with SMTP id r18so5540347wmd.3 for ; Wed, 01 Feb 2017 04:45:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; 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=uJktU6OMmYfSLl7oQ542Ah9jkxYQo/eyvRHBNlfb2A0=; b=laUSoxgEgE8sCWPsi5EliaeOb8ZtBrUevoVbz3N0RCJ4N6xBhCVrEGEj2cK61aWe9r PC52uTGDWvWjcMOgo0uEadOapVre1ASramyXdwvOLaTsvq5WqEOTnpRr/y1YtXERJFc0 xfhcDlP2sDHbEcZnAU70cuMZDl82zEYGaXljY7F6LePGx9DbpBRDFR6RVnA+16b91mmv PI+toWnqVoYYglHx0fWx3ZurPoGM3eeEOa5RYsXlSAI4Gy75h2Me9VJxyxJp/NdA+WEU dHu811A1ksdmnboMK1+BfT2/IIYOlzx4/2z9KlkJcju8/tbBbalsolUWWr4i5y5w/UPn uGpA== X-Gm-Message-State: AIkVDXLy/0a0yA9OOYB9+adWMzeb5mveVUXeNsI19E/Ady6Nw1lFnBUs1EM8uaQz9ajSiA== X-Received: by 10.28.146.12 with SMTP id u12mr2865082wmd.113.1485953099440; Wed, 01 Feb 2017 04:44:59 -0800 (PST) Received: from E107787-LIN ([194.214.185.158]) by smtp.gmail.com with ESMTPSA id a186sm29449458wmh.1.2017.02.01.04.44.58 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Wed, 01 Feb 2017 04:44:58 -0800 (PST) Date: Wed, 01 Feb 2017 12:45:00 -0000 From: Yao Qi To: Pedro Alves Cc: Alan Hayward , "gdb-patches@sourceware.org" Subject: Re: [PATCH] Removal of uses of MAX_REGISTER_SIZE Message-ID: <20170201124123.GA27498@E107787-LIN> References: <7CF07197-4FED-4970-BB4B-2FE828E29A63@arm.com> <45e3a5e1-a9aa-1bc0-5d08-526b89fc458e@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <45e3a5e1-a9aa-1bc0-5d08-526b89fc458e@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2017-02/txt/msg00019.txt.bz2 On 17-01-27 12:11:09, Pedro Alves wrote: > > Makes me wonder whether this is the right approach. :-/ > (No, I don't have a formed opinion for what that would be.) > Hi Pedro, What do you mean by "this" here? We can't take MAX_REGISTER_SIZE for ever, as we may have bigger and bigger single register. We do need a gdbarch specific max register size. Given there is no standard VLA in C++, using alloca is the best way we can do so far. -- Yao (齐尧)