From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ok+IBMEIk2B8DQAAWB0awg (envelope-from ) for ; Wed, 05 May 2021 17:06:09 -0400 Received: by simark.ca (Postfix, from userid 112) id 052701F11C; Wed, 5 May 2021 17:06:09 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_SIGNED, MAILING_LIST_MULTI,RDNS_DYNAMIC,T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 22D1E1E813 for ; Wed, 5 May 2021 17:06:08 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id BE2EE385482A; Wed, 5 May 2021 21:06:07 +0000 (GMT) Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by sourceware.org (Postfix) with ESMTPS id BE338385482A for ; Wed, 5 May 2021 21:06:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org BE338385482A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=sifive.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=jimw@sifive.com Received: by mail-ej1-x62d.google.com with SMTP id u3so4971192eja.12 for ; Wed, 05 May 2021 14:06:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DtcnmKlcHuNvyT07cVh35oPWhcLTjVBYsR8/dcxnxUY=; b=b3nryIYf1unhLll0KXBo5M/KokYBxOnI63hRWZbyRrhhvRy5KonvlJj4limQod5GVi G1rTN7MiGa/ZMm7F5pqd1NDmZUAR2LZyyLwlkMFiX1fofnM5ATqD1sfJ4kKBMEoJnOba PBPO/Q+XfTu5+WYjgO+8j6eemnl+wdDuQLiICx286Sfbc2O7kSOE+K1LghT9dLUdSbJn OZ23MTOv769TTSrE75v/dQaiyOREF/DxNBfy7/2JToFfABlDtWgTiQPF/TUSAUMxkmCt hjkGoNpcFJ7gMiJ/Md+02+rtaMW/lZJj5dLMOtozwsxSJAHJxHZpiYASuKNm674dbiWw IC5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DtcnmKlcHuNvyT07cVh35oPWhcLTjVBYsR8/dcxnxUY=; b=ht+5Y31IoJdV13yXG/U2exsrHglDmLd2WaPNte99tQ62Ga6KOoly5SU9gQhL7RX0G9 uJsLOzk6x2c19X8JocDwXL8CgfeIq+x979DvAaiF73PMvQICY/JBWGNtsJP0mazesDsc NpAjaFtntNVq6977CRbdGYGrbhj9XKzUAud3QXjtQcbUZRqpyyzydv59R8+i3i7W9Vz0 c3fA97zvsjqgsefNI84fL0FT7YPAF7EZOU9SKxDKaL+hzy77xGhmzK3kHj0gbom+Zsf2 w1bYz4WYluxWEkELqQ/rMkv2YuWdhSRiDKL8p7qpXdhbUBiy0dZzoxPdfSjaW31mBl6L CIPA== X-Gm-Message-State: AOAM532bs7ukZbnFc+wtOZYlOhm55vb4CgEoP4rb7k8QspUgSUUYE831 Qtfq4QOd7xjL9lA6REUnMUEFBEOsZnSjLe8X8empKg== X-Google-Smtp-Source: ABdhPJwxZmKtCrzWBG0oVWx/NRkaRn/g1xOAG13oZwgBMY0BY2Q9OiIHZ+LGTAVmfLg8UkNoFEUfh7l3v2ixenSe38A= X-Received: by 2002:a17:906:1fca:: with SMTP id e10mr709614ejt.486.1620248763752; Wed, 05 May 2021 14:06:03 -0700 (PDT) MIME-Version: 1.0 References: <20210505094639.1551740-1-andrew.burgess@embecosm.com> In-Reply-To: <20210505094639.1551740-1-andrew.burgess@embecosm.com> From: Jim Wilson Date: Wed, 5 May 2021 14:05:52 -0700 Message-ID: Subject: Re: [PATCH] gdb/riscv: add support for vector registers in target descriptions To: Andrew Burgess Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" On Wed, May 5, 2021 at 2:46 AM Andrew Burgess wrote: > This commit adds support to RISC-V GDB for vector registers in the > incoming target description. > It looks reasonable to me. Though I did notice that you have two comments which mention f-register instead of v-register. The vector spec isn't official yet, and hasn't been frozen yet, so there is a chance that some things will still change, but very unlikely that this patch would be affected. I can't imagine them changing the number of user registers at this point. Jim