public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <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: Wed, 23 Nov 2022 22:26:06 +0000	[thread overview]
Message-ID: <bug-29816-4717-a9sLq4S9BI@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 #7 from Carl E Love <cel at us dot ibm.com> ---
I tried the fix on Power 9 and Power 10.  I see the same results with and
without the patch. 

make check RUNTESTFLAGS='GDB=/home/carll/bin/gdb gdb.ada/float-bits.exp '

The contents of gdb/testsuite/gdb.log:

print val_double^M
$8 = -2.0e-19^M
(gdb) PASS: gdb.ada/float-bits.exp: print val_double after assignment
ptype long_long_float^M
type = <8-byte float>^M
(gdb) ptype 16llf#0#^M
type = <16-byte float>^M
(gdb) print 16llf#4000921fb54442d18469898cc51701b8#^M
$9 = <invalid float value>^M
(gdb) FAIL: gdb.ada/float-bits.exp: print
16llf#4000921fb54442d18469898cc51701b8#
print $foo:=16llf#4000921fb54442d18469898cc51701b8#^M
$10 = <invalid float value>^M
(gdb) FAIL: gdb.ada/float-bits.exp: print
$foo:=16llf#4000921fb54442d18469898cc51701b8#
print $foo^M
$11 = <invalid float value>^M
(gdb) FAIL: gdb.ada/float-bits.exp: print internal long double variable after
assignment
testcase
/home/carll/GDB/build-current/gdb/testsuite/../../../binutils-gdb-current/gdb/testsuite/gdb.ada/float-bits.exp
c\
ompleted in 0 seconds

                === gdb Summary ===

# of expected passes            9
# of unexpected failures        3



You mentioned OBS, what is that? Perhaps there is something different in our
environments??

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

  parent reply	other threads:[~2022-11-23 22:26 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 [this message]
2022-11-24  6:27 ` vries at gcc dot gnu.org
2022-11-24 13:00 ` vries at gcc dot gnu.org
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-a9sLq4S9BI@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).