From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Gustavo Romero <gustavo.romero@linaro.org>,
qemu-arm@nongnu.org, Anton Johansson <anjo@rev.ng>
Subject: Re: [PATCH 0/2] target/arm: Always build Aarch64 gdbstub helpers
Date: Fri, 28 Jun 2024 09:50:21 -0700 [thread overview]
Message-ID: <ebfa6ca6-d93e-45b3-8786-cb52505e2d7c@linaro.org> (raw)
In-Reply-To: <83667101-daba-43ea-ba33-1df547020cd9@linaro.org>
On 6/28/24 09:37, Philippe Mathieu-Daudé wrote:
> On 28/6/24 16:31, Richard Henderson wrote:
>> On 6/19/24 05:49, Philippe Mathieu-Daudé wrote:
>>> Merge gdbstub64.c in gdbstub.c and remove uses of
>>> target specific TARGET_AARCH64 definition.
>>> Small step toward single ARM/Aarch64 binary.
>>>
>>> Philippe Mathieu-Daudé (2):
>>> target/arm: Merge gdbstub64.c within gdbstub.c
>>> target/arm: Always build Aarch64 gdbstub helpers
>>>
>>> target/arm/cpu.h | 8 +-
>>> target/arm/internals.h | 2 -
>>> target/arm/gdbstub.c | 363 +++++++++++++++++++++++++++++++++++++-
>>> target/arm/gdbstub64.c | 383 -----------------------------------------
>>> target/arm/meson.build | 1 -
>>> 5 files changed, 364 insertions(+), 393 deletions(-)
>>> delete mode 100644 target/arm/gdbstub64.c
>>>
>>
>> Are we attempting a single binary for user-only as well?
>
> No, due to ABI constraints, right? I did a user-emulation
> smoke build, no failure, did I miss something?
Well, no. But qemu-arm does not need gdbstub64.c.
Given TARGET_AARCH64 will be set on a combined build, I'm not sure what is the fix?
r~
next prev parent reply other threads:[~2024-06-28 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:49 [PATCH 0/2] target/arm: Always build Aarch64 gdbstub helpers Philippe Mathieu-Daudé
2024-06-19 12:49 ` [PATCH 1/2] target/arm: Merge gdbstub64.c within gdbstub.c Philippe Mathieu-Daudé
2024-06-19 12:49 ` [PATCH 2/2] target/arm: Always build Aarch64 gdbstub helpers Philippe Mathieu-Daudé
2024-06-28 6:19 ` [PATCH 0/2] " Philippe Mathieu-Daudé
2024-06-28 14:31 ` Richard Henderson
2024-06-28 16:37 ` Philippe Mathieu-Daudé
2024-06-28 16:50 ` Richard Henderson [this message]
2024-07-04 15:01 ` Peter Maydell
2024-07-04 18:24 ` Richard Henderson
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=ebfa6ca6-d93e-45b3-8786-cb52505e2d7c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=anjo@rev.ng \
--cc=gustavo.romero@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.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).