From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, "Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [RFC PATCH] gdbstub: attempt to split gdb into 32/64 bit targets [!WORKING PLZ HELP]
Date: Thu, 2 Mar 2023 16:38:57 -0800 [thread overview]
Message-ID: <7823fa02-08fd-4130-cea3-f44b8c51d584@linaro.org> (raw)
In-Reply-To: <20230302192546.2617633-1-alex.bennee@linaro.org>
On 3/2/23 09:25, Alex Bennée wrote:
> Instead of building gdb syscalls for every target only build what
> really matters, 64 or 32 bit support.
Since the *only* usage of target_ulong is in the va_list for gdb_do_syscall, and as that
passes on to printf, we could just adjust the interface to always pass uint64_t.
r~
prev parent reply other threads:[~2023-03-03 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 19:25 [RFC PATCH] gdbstub: attempt to split gdb into 32/64 bit targets [!WORKING PLZ HELP] Alex Bennée
2023-03-02 23:21 ` Richard Henderson
2023-03-02 23:56 ` Richard Henderson
2023-03-03 0:38 ` Richard Henderson [this message]
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=7823fa02-08fd-4130-cea3-f44b8c51d584@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).