public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29816] [gdb/testsuite, powerpc64le] FAIL: gdb.ada/float-bits.exp: print 16llf#4000921fb54442d18469898cc51701b8#
Date: Thu, 24 Nov 2022 13:00:02 +0000	[thread overview]
Message-ID: <bug-29816-4717-Sw2lyGD9sT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29816-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29816

--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
I start to wonder whether we should give up trying to hardcode these hex
numbers, and just work with whatever is printed for "p /x Val_Long_Double".

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-11-24 13:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 14:10 [Bug tdep/29816] New: [gdb/tdep, " vries at gcc dot gnu.org
2022-11-21 17:45 ` [Bug tdep/29816] " vries at gcc dot gnu.org
2022-11-21 17:50 ` vries at gcc dot gnu.org
2022-11-21 18:00 ` vries at gcc dot gnu.org
2022-11-23 11:21 ` [Bug testsuite/29816] [gdb/testsuite, " vries at gcc dot gnu.org
2022-11-23 16:01 ` tromey at sourceware dot org
2022-11-23 17:01 ` vries at gcc dot gnu.org
2022-11-23 22:26 ` cel at us dot ibm.com
2022-11-24  6:27 ` vries at gcc dot gnu.org
2022-11-24 13:00 ` vries at gcc dot gnu.org [this message]
2022-11-30 14:00 ` vries at gcc dot gnu.org
2022-12-01  6:25 ` cvs-commit at gcc dot gnu.org
2022-12-01  6:27 ` vries at gcc dot gnu.org

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=bug-29816-4717-Sw2lyGD9sT@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).