Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: introduce command "info architecture"
Date: Sat, 8 Nov 2025 02:25:41 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.21.2511080203210.25436@angie.orcam.me.uk> (raw)
In-Reply-To: <9c11ee0a-d4f6-4628-8aaf-e2e317e871bb@redhat.com>

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. <https://en.wikipedia.org/wiki/Microarchitecture> for an overview.

 I think the GDB manual has been pretty correct in its "architecture" term
usage.

  Maciej

  parent reply	other threads:[~2025-11-08  2:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 19:45 [PATCH 0/2] Add warning if the native target is not supported Guinevere Larsen
2025-11-06 19:45 ` [PATCH 1/2] gdb: introduce command "info architecture" Guinevere Larsen
2025-11-06 23:24   ` Maciej W. Rozycki
2025-11-07 13:10     ` Guinevere Larsen
2025-11-07 15:51       ` Maciej W. Rozycki
2025-11-07 16:05         ` Hannes Domani
2025-11-08  2:02           ` Maciej W. Rozycki
2025-11-27 19:51         ` Guinevere Larsen
2025-11-27 20:00           ` Maciej W. Rozycki
2025-11-27 20:09             ` Guinevere Larsen
2025-11-28  9:20               ` Maciej W. Rozycki
2025-12-01 16:49                 ` Guinevere Larsen
2025-11-07  7:46   ` Eli Zaretskii
2025-11-07 13:41     ` Guinevere Larsen
2025-11-07 14:23       ` Eli Zaretskii
2025-11-08  2:25       ` Maciej W. Rozycki [this message]
2025-11-27 20:01         ` Guinevere Larsen
2025-11-28  9:20           ` Maciej W. Rozycki
2025-11-06 19:45 ` [PATCH 2/2] gdb: add warning when no native target is available Guinevere Larsen
2025-11-07  7:48   ` Eli Zaretskii
2025-11-07 13:24     ` Guinevere Larsen
2025-11-07 14:21       ` Eli Zaretskii
2025-11-27 20:15         ` Guinevere Larsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.2511080203210.25436@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox