qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
	"open list:ARM TCG CPUs" <qemu-arm@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: [PATCH  v3 10/12] target/arm: don't expose "ieee_half" via gdbstub
Date: Fri,  3 Apr 2020 20:11:48 +0100	[thread overview]
Message-ID: <20200403191150.863-11-alex.bennee@linaro.org> (raw)
In-Reply-To: <20200403191150.863-1-alex.bennee@linaro.org>

While support for parsing ieee_half in the XML description was added
to gdb in 2019 (a6d0f249) there is no easy way for the gdbstub to know
if the gdb end will understand it. Disable it for now and allow older
gdbs to successfully connect to the default -cpu max SVE enabled
QEMUs.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
---
 target/arm/gdbstub.c | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/target/arm/gdbstub.c b/target/arm/gdbstub.c
index d9ef7d2187c..8efc535f2a0 100644
--- a/target/arm/gdbstub.c
+++ b/target/arm/gdbstub.c
@@ -192,7 +192,12 @@ static const struct TypeSize vec_lanes[] = {
     /* 16 bit */
     { "uint16", 16, 'h', 'u' },
     { "int16", 16, 'h', 's' },
-    { "ieee_half", 16, 'h', 'f' },
+    /*
+     * TODO: currently there is no reliable way of telling
+     * if the remote gdb actually understands ieee_half so
+     * we don't expose it in the target description for now.
+     * { "ieee_half", 16, 'h', 'f' },
+     */
     /* bytes */
     { "uint8", 8, 'b', 'u' },
     { "int8", 8, 'b', 's' },
-- 
2.20.1



  parent reply	other threads:[~2020-04-03 19:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 19:11 [PATCH v3 for 5.0-rc2 00/12] a selection of random fixes Alex Bennée
2020-04-03 19:11 ` [PATCH v3 01/12] elf-ops: bail out if we have no function symbols Alex Bennée
2020-04-03 19:11 ` [PATCH v3 02/12] linux-user: protect fcntl64 with an #ifdef Alex Bennée
2020-04-03 19:11 ` [PATCH v3 03/12] tests/tcg: remove extraneous pasting macros Alex Bennée
2020-04-03 19:11 ` [PATCH v3 04/12] linux-user: more debug for init_guest_space Alex Bennée
2020-04-03 20:39   ` Philippe Mathieu-Daudé
2020-04-03 19:11 ` [PATCH v3 05/12] target/xtensa: add FIXME for translation memory leak Alex Bennée
2020-04-03 19:11 ` [PATCH v3 06/12] gdbstub: fix compiler complaining Alex Bennée
2020-04-06 10:21   ` Chenqun (kuhn)
2020-04-03 19:11 ` [PATCH v3 07/12] softfloat: Fix BAD_SHIFT from normalizeFloatx80Subnormal Alex Bennée
2020-04-03 19:11 ` [PATCH v3 08/12] linux-user: factor out reading of /proc/self/maps Alex Bennée
2020-04-04  0:33   ` Richard Henderson
2020-04-06  9:09     ` Alex Bennée
2020-04-03 19:11 ` [PATCH v3 09/12] linux-user: clean-up padding on /proc/self/maps Alex Bennée
2020-04-03 19:11 ` Alex Bennée [this message]
2020-04-03 19:11 ` [PATCH v3 11/12] hw/core: properly terminate loading .hex on EOF record Alex Bennée
2020-04-03 19:11 ` [PATCH v3 12/12] configure: Add -Werror to PIE probe Alex Bennée
2020-04-06 21:32   ` Philippe Mathieu-Daudé

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=20200403191150.863-11-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).