Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Sven Schnelle <svens@stackframe.org>, gdb-patches@sourceware.org
Cc: Helge Deller <deller@gmx.de>,
	John David Anglin <dave.anglin@bell.net>,
	binutils@sourceware.org
Subject: Re: [PATCH v2] gdb/hppa: guess g packet size
Date: Mon, 10 Nov 2025 12:09:04 -0500	[thread overview]
Message-ID: <80bc91f7-5899-48f4-b638-59e58578dc20@simark.ca> (raw)
In-Reply-To: <dd1b4b7c-8454-4cfd-80d7-d8ce2c589a5f@simark.ca>

On 11/10/25 11:52 AM, Simon Marchi wrote:
> I'm not super familiar with remote target descriptions, here's my
> understanding of what is happening, please let me know if this is
> correct.  The target descriptions you create are never actually used are
> target descriptions, but are just some "flags" to indicate whether the g
> packet size guess resulted in 32 or 64.  It seems a bit silly / strange
> to use a target description this way, but perhaps there's no better way
> with what we currently have.  Are there other arches in GDB that work
> this way, that I could reference as "prior art"?

Actually, I checked it myself, it's not too difficult.  It seems like
MIPS does something like that, although it also seems to support "real"
target descriptions, given it does:

  /* Check any target description for validity.  */
  if (tdesc_has_registers (info.target_desc))
    ...

I also checked QEMU's repo [1], it doesn't seem to have a target
description for the hppa architecture.

[1] https://github.com/qemu/qemu/tree/593aee5df98b4a862ff8841a57ea3dbf22131a5f/gdb-xml

Simon

  reply	other threads:[~2025-11-10 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  6:30 Sven Schnelle
2025-11-10 13:47 ` Sven Schnelle
2025-11-10 16:52 ` Simon Marchi
2025-11-10 17:09   ` Simon Marchi [this message]
2025-11-10 17:21   ` Sven Schnelle
2025-11-10 17:38     ` Simon Marchi
2025-11-10 20:10       ` Sven Schnelle
2025-11-10 20:29         ` Simon Marchi

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=80bc91f7-5899-48f4-b638-59e58578dc20@simark.ca \
    --to=simark@simark.ca \
    --cc=binutils@sourceware.org \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=gdb-patches@sourceware.org \
    --cc=svens@stackframe.org \
    /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