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] [gdb, testsuite/aarch64] FAIL: gdb.ada/literals.exp: print 16#ffffffffffffffff# Date: Wed, 27 Jul 2022 10:09:52 +0000 [thread overview] Message-ID: <bug-29416-4717-cA1IaJBNPy@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29416-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29416 --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- With i386, we have: ... (gdb) p int_bits $3 = 32 (gdb) p long_bits $4 = 32 (gdb) p long_long_bits $5 = 64 ... so in processInt we hit the fits-in-unsigned-long-long case where we use as type long long, so we have: ... /* Note: Interprets ULLONG_MAX as -1. */ yylval.typed_val.type = type_long_long (par_state); ... With aarch64, we have: ... (gdb) p int_bits $1 = 32 (gdb) p long_bits $2 = 64 (gdb) p long_long_bits $3 = 64 ... so in processInt we hit the fits-in-unsigned-long case and we use type unsigned long: ... yylval.typed_val.type = builtin_type (par_state->gdbarch ())->builtin_unsigned_long; ... This explains the difference between the two results. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-27 10:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-27 9:56 [Bug testsuite/29416] New: " vries at gcc dot gnu.org 2022-07-27 10:09 ` vries at gcc dot gnu.org [this message] 2022-07-27 10:35 ` [Bug testsuite/29416] " 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-cA1IaJBNPy@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).