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/29416] New: [gdb, testsuite/aarch64] FAIL: gdb.ada/literals.exp: print 16#ffffffffffffffff# Date: Wed, 27 Jul 2022 09:56:15 +0000 [thread overview] Message-ID: <bug-29416-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29416 Bug ID: 29416 Summary: [gdb, testsuite/aarch64] FAIL: gdb.ada/literals.exp: print 16#ffffffffffffffff# Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- On aarch64, I run into: ... (gdb) print 16#ffffffffffffffff#^M $7 = 18446744073709551615^M (gdb) FAIL: gdb.ada/literals.exp: print 16#ffffffffffffffff# ... On x86_64 instead, I get: ... (gdb) print 16#ffffffffffffffff#^M $7 = -1^M (gdb) PASS: gdb.ada/literals.exp: print 16#ffffffffffffffff# ... I can reproduce this on x86_64-linux using: ... $ gdb -q -batch -ex "set lang ada" -ex "set arch i386" -ex "print 16#ffffffffffffffff#" The target architecture is set to "i386". $1 = -1 $ gdb -q -batch -ex "set lang ada" -ex "set arch aarch64" -ex "print 16#ffffffffffffffff#" The target architecture is set to "aarch64". $1 = 18446744073709551615 ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-27 9:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-27 9:56 vries at gcc dot gnu.org [this message] 2022-07-27 10:09 ` [Bug testsuite/29416] " vries at gcc dot gnu.org 2022-07-27 10:35 ` vries at gcc dot gnu.org 2022-07-29 14:30 ` vries at gcc dot gnu.org 2022-07-30 6:03 ` [Bug ada/29416] " 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-29416-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).