From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id E2uyKIw/OGSJ6yoAWB0awg (envelope-from ) for ; Thu, 13 Apr 2023 13:44:44 -0400 Received: by simark.ca (Postfix, from userid 112) id 9A1261E221; Thu, 13 Apr 2023 13:44:44 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=jgAvTvxo; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.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 2DE1B1E110 for ; Thu, 13 Apr 2023 13:44:44 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id B0D6C3858C60 for ; Thu, 13 Apr 2023 17:44:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B0D6C3858C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681407882; bh=KMt769h2U0liuywwCJAtBgjR1b+bqK6UTvIb9D/8bpE=; h=Date:To:Cc:In-Reply-To:Subject:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=jgAvTvxo4qrYcim2S+yoTh/KErN9VdsNVWksr5ik3IoiWL+vU7a9yZp6A7yiLSz8C 7jU6lqoP1crs0h/LIi8mXicxifytDa9NhuG0NJjc7NtXkBoxeHYy5IiWXrKB/2R+vX 7XagE5pcmHDd0G0/yyHWQyGmzhbxBGFS7q7naR0Q= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 1CF3B3858D20 for ; Thu, 13 Apr 2023 17:44:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1CF3B3858D20 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pn0zb-0006bN-LI; Thu, 13 Apr 2023 13:44:19 -0400 Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pn0zY-0004ev-Ut; Thu, 13 Apr 2023 13:44:17 -0400 Date: Thu, 13 Apr 2023 20:45:04 +0300 Message-Id: <83h6tj4qxr.fsf@gnu.org> To: Luis Machado Cc: gdb-patches@sourceware.org In-Reply-To: <56b69866-8f70-3bed-0645-79dcc4a99f23@arm.com> (message from Luis Machado on Thu, 13 Apr 2023 17:34:17 +0100) Subject: Re: [PATCH,v2 17/17] [gdb/docs] sme: Document SME registers and features References: <20230411042658.1852730-18-luis.machado@arm.com> <20230412120444.2593312-1-luis.machado@arm.com> <835ya05i4r.fsf@gnu.org> <83leiv4xsc.fsf@gnu.org> <56b69866-8f70-3bed-0645-79dcc4a99f23@arm.com> 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: , From: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > Date: Thu, 13 Apr 2023 17:34:17 +0100 > Cc: gdb-patches@sourceware.org > From: Luis Machado > > I may have made a few mistakes before using lower case svq and svl, which should now be > fixed in the upcoming version. Before I send an update though, I'd like to clarify > the terminology and how I'm using it. Just a sanity check that it isn't confusing still. > > SVG, SVQ and SVL (upper case) are only definitions for SME. SVL is the vector size in bytes, > SVG is SVL / 8 and SVQ is SVL / 16. All of them are vector sizes, but with different > granularities. > > GDB exposes the SME vector size SVG as the svg (lower case) register, so users can check the > current vector size and change it if they want. > > In the end, we have 3 definitions and a register. > > Does that make sense? I understand the terminology you want to use. > > My main point was that it is easier and clearer to say ABCxABC than to > > use some unrelated symbol N and then explain that N equals to the > > parameter ABC. But it's a minor issue. > > > > That's fair. I find that slightly confusing too. What we should say, based on the > SME vector size definitions above is: > > The @code{za} register is a 2-dimensional square > @code{@var{SVL}x@var{SVL}} matrix of bytes. > > That makes it clear and obvious (to me) that we have a matrix of size > SVL x SVL bytes. Yes, but please note that the argument of @var should a lower-case word. In Info format, it is up-cases, but in HTML and PDF it's typeset in slant typeface, and not up-cased. This is actually one place where using SVL and SVG as parameters gets in the way: you spell them in upper-case, which is against the practice of using @var. > > Then please say that without using the word "same" on its own. "Same" > > begs the question "same as what?", which doesn't have an answer in > > this context. > > > > Ok. I think something like the following might address your concerns? > > Attempting to set the @code{svg} register value to its current value will have no effect. Yes, this is okay. Thanks.