public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	will_schmidt_vnet.ibm.com <will_schmidt@vnet.ibm.com>,
	"cel@us.ibm.com" <cel@us.ibm.com>
Cc: Rogerio Alves Cardoso <rogealve@br.ibm.com>,
	"tromey@adacore.com" <tromey@adacore.com>
Subject: Re: [PATCH V2] Powerpc: Update expected floating point output for gdb.arch/altivec-regs.exp and gdb.arch/vsx-regs.exp
Date: Tue, 26 Apr 2022 14:28:34 +0000	[thread overview]
Message-ID: <c9e7631b4de85b817367bd36dbb1d690ac303bcf.camel@de.ibm.com> (raw)
In-Reply-To: <cd3bb2935cb0c5dd2b3388984708df91670408c0.camel@us.ibm.com>

Carl Love <cel@us.ibm.com> wrote:

>PowerPC: Update expected floating point output for gdb.arch/altivec-
>regs.exp and gdb.arch/vsx-regs.exp

This patch is OK.

As additional comment, I'm wondering whether the display of vector
registers via the union we're using is actually useful when in
hexadecimal mode.  The intent of the union is that it should be easy to
interpret the register contents in various ways, in particular both as
integer and as floating-point value, as we may not know what type is
currently being held in the register.

However, with the new way of printing floating-point values when /x is
in effect, it seems that the contents of v4_float will now always be
identical to v4_int32, and similar for the other floating-point union
members.

So maybe it would be better to always show the floating-point members
as actual floating-point, even when the rest of the union is printed
via /x.  However, that may be a more invasive change, so I think you
should go ahead and commit the patch as-is now, to improve the
testsuite results.

Bye,
Ulrich


  parent reply	other threads:[~2022-04-26 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12  4:47 Carl Love
2022-04-18 16:20 ` will schmidt
2022-04-18 20:04   ` [PATCH V2] " Carl Love
2022-04-22 19:50     ` [PATCH V2 Ping] " Carl Love
2022-04-26 14:28     ` Ulrich Weigand [this message]
2022-04-26 17:24       ` [PATCH V2] " Carl Love

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=c9e7631b4de85b817367bd36dbb1d690ac303bcf.camel@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=cel@us.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=rogealve@br.ibm.com \
    --cc=tromey@adacore.com \
    --cc=will_schmidt@vnet.ibm.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).