From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id iHspL0+qDmld7ioAWB0awg (envelope-from ) for ; Fri, 07 Nov 2025 21:26:23 -0500 Received: by simark.ca (Postfix, from userid 112) id B17C51E04C; Fri, 07 Nov 2025 21:26:23 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,RCVD_IN_VALIDITY_RPBL_BLOCKED, RCVD_IN_VALIDITY_SAFE_BLOCKED autolearn=ham autolearn_force=no version=4.0.1 Received: from server2.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 ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 046C61E04C for ; Fri, 07 Nov 2025 21:26:23 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 552433858CD9 for ; Sat, 8 Nov 2025 02:26:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 552433858CD9 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by sourceware.org (Postfix) with ESMTP id 946A63858D35 for ; Sat, 8 Nov 2025 02:25:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 946A63858D35 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=orcam.me.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=orcam.me.uk ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 946A63858D35 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2001:4190:8020::34 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1762568742; cv=none; b=hWrgVRfeyxUxOSRXoFyuVb8zO/faUPP/+Pjwap5zQFtKjQNdMT1DdlomwmHeHeN8H3pLxSToTV8mOZ1Axp3ZjyV+vcC8Gwb+4bTh7GHxw625gxxzRx1R1it99CC4VDSACSo+2ui/PCKlC7YWHP2xy6meQ9gaLJH4h9BRqlwvZDs= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1762568742; c=relaxed/simple; bh=+LDO9bBt9ZT8wkCfysVrrBxzE5YxgP/Oe0hYZ7FOasM=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=pT56/ksTTgfE5D7IAeK/uXO9/9krHQrs5DehPt77DPPD/YpZm2wKhRxr+dJ3roYg5rM9WJW/8goukXjdUzcr3SZZ037LsWcEeTnbGJNz3zTb5xyDFWweZglPQI/iJJbUY6RSmlegU+f1ZMgweM/DXfUsadKzdkfQ/8V1KvrJwLU= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 946A63858D35 Received: by angie.orcam.me.uk (Postfix, from userid 500) id 0C1E292009D; Sat, 8 Nov 2025 03:25:42 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 0295092009C; Sat, 8 Nov 2025 02:25:41 +0000 (GMT) Date: Sat, 8 Nov 2025 02:25:41 +0000 (GMT) From: "Maciej W. Rozycki" To: Guinevere Larsen cc: Eli Zaretskii , gdb-patches@sourceware.org Subject: Re: [PATCH 1/2] gdb: introduce command "info architecture" In-Reply-To: <9c11ee0a-d4f6-4628-8aaf-e2e317e871bb@redhat.com> Message-ID: References: <20251106194514.1857177-1-guinevere@redhat.com> <20251106194514.1857177-2-guinevere@redhat.com> <865xbmb7z2.fsf@gnu.org> <9c11ee0a-d4f6-4628-8aaf-e2e317e871bb@redhat.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org On Fri, 7 Nov 2025, Guinevere Larsen wrote: > > Thanks. The documentation parts are okay (with one nit, see below), > > but I'm struggling to understand what you mean by "CPU > > microarchitectures". And without examples, I cannot even guess. > > Would it be possible to expand on that in the manual, or at least > > provide a could of examples of what the output will look like? > > A CPU architecture is something like "arm" or "x86". The microarchitecture is > changes within that architecture, like "armv3", "armv4", "armv3m" and so on. I don't think it's correct, not at least it's the definition I've been taught. In my dictionary microarchitecture is a particular implementation of a given architecture with all its properties, such as instruction latencies, the execution units and pipeline stages, the existence or the lack of specific pipeline dependencies, and so on and so on. I can't comment on ARM particulars as I'm not very familiar with them, but offhand "armv3" or "armv4" seem to me to be architecture revisions rather than microarchitectures. In MIPS terms MIPS is the target architecture, MIPS32r2 is a particular architecture revision ("mips:isa32r2" in terms of `set architecture') and 24Kf or 74Kf are microarchitectures, both implementing the MIPS32r2 architecture. Cf. for an overview. I think the GDB manual has been pretty correct in its "architecture" term usage. Maciej