Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Ezra Sitorus <ezra.sitorus@arm.com>
Cc: Tom Tromey <tom@tromey.com>,  <gdb-patches@sourceware.org>,
	<luis.machado.foss@gmail.com>,  <pedro@palves.net>
Subject: Re: [RFC PATCH] gdb/py: Add pretty printer for __mfp8 for aarch64
Date: Wed, 19 Nov 2025 08:58:05 -0700	[thread overview]
Message-ID: <87qztuqak2.fsf@tromey.com> (raw)
In-Reply-To: <aR3CIdIzSdxRxqBw@D2G2X7XGD1> (Ezra Sitorus's message of "Wed, 19 Nov 2025 13:12:01 +0000")

>>>>> "Ezra" == Ezra Sitorus <ezra.sitorus@arm.com> writes:

>> Can the compiler be fixed to emit correct DWARF instead?  That seems
>> like it would be a lot better, and in keeping with the purpose of DWARF.

Ezra> GCC encodes __mfp8 as a uint, while Clang encodes it as unsigned char. 
Ezra> Even if we were to focus on just GCC, __mfp8 is typedef'd as uint8_t so
Ezra> I don't think we can emit a float type. Or is there something else I'm
Ezra> overlooking?

I don't really know anything about this type.  Could you say what it
really is?

If it's just a float of some kind, then I don't see why it couldn't be
emitted that way (i.e., base type with DW_ATE_Float and the appropriate
size), and then if gdb needs special support, that could be added using
the usual approach (floatformat or whatever).

Tom

  reply	other threads:[~2025-11-19 15:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 14:14 Ezra.Sitorus
2025-11-18 17:12 ` Andrew Burgess
2025-11-18 18:37   ` Ezra Sitorus
2025-11-26 16:08   ` Ezra Sitorus
2025-11-18 18:42 ` Tom Tromey
2025-11-19 13:12   ` Ezra Sitorus
2025-11-19 15:58     ` Tom Tromey [this message]
2025-11-19 21:28       ` Ezra Sitorus
2025-12-16 16:39       ` Ezra Sitorus

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=87qztuqak2.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=ezra.sitorus@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado.foss@gmail.com \
    --cc=pedro@palves.net \
    /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