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 tdep/29816] New: [gdb/tdep, powerpc64le] FAIL: gdb.ada/float-bits.exp: print 16llf#4000921fb54442d18469898cc51701b8# Date: Mon, 21 Nov 2022 14:10:19 +0000 [thread overview] Message-ID: <bug-29816-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29816 Bug ID: 29816 Summary: [gdb/tdep, powerpc64le] FAIL: gdb.ada/float-bits.exp: print 16llf#4000921fb54442d18469898cc51701b8# Product: gdb Version: 12.1 Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- In OBS, with a gdb 12.1 based package, on ppc64le, I run into: ... FAIL: gdb.ada/float-bits.exp: print 16llf#4000921fb54442d18469898cc51701b8# FAIL: gdb.ada/float-bits.exp: print $foo:=16llf#4000921fb54442d18469898cc51701b8# FAIL: gdb.ada/float-bits.exp: print internal long double variable after assignment ... In more detail: ... (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 ... I have some hope these are no longer reproducible with master, but I'm having trouble installing an ada compiler on my powerpc64le box (so, outside OBS) to verify this, so I'm filing this not to lose track of this. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-11-21 14:10 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-21 14:10 vries at gcc dot gnu.org [this message] 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 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@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: linkBe 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).