public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dmitry.neverov at jetbrains dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30445] New: Missing structure for ymm{N}h register values on x86-64 Date: Mon, 15 May 2023 07:02:51 +0000 [thread overview] Message-ID: <bug-30445-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30445 Bug ID: 30445 Summary: Missing structure for ymm{N}h register values on x86-64 Product: gdb Version: 13.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dmitry.neverov at jetbrains dot com Target Milestone: --- Gdb provides structure for register values, e.g. for xmm0 gdb/mi returns: -data-list-register-values --thread 1 --frame 0 --skip-unavailable r 40 ^done,register-values=[{number="40",value="{v8_bfloat16 = {0x92a0, 0x5555, 0x5555, 0x0000, 0x92a0, 0x5555, 0x5555, 0x0000}, v8_half = {0x92a0, 0x5555, 0x5555, 0x0000, 0x92a0, 0x5555, 0x5555, 0x0000}, v4_float = {0x555592a0, 0x00005555, 0x555592a0, 0x00005555}, v2_double = {0x00005555555592a0, 0x00005555555592a0}, v16_int8 = {0xa0, 0x92, 0x55, 0x55, 0x55, 0x55, 0x00, 0x00, 0xa0, 0x92, 0x55, 0x55, 0x55, 0x55, 0x00, 0x00}, v8_int16 = {0x92a0, 0x5555, 0x5555, 0x0000, 0x92a0, 0x5555, 0x5555, 0x0000}, v4_int32 = {0x555592a0, 0x00005555, 0x555592a0, 0x00005555}, v2_int64 = {0x00005555555592a0, 0x00005555555592a0}, uint128 = 0x00005555555592a000005555555592a0}"}] When ymm0h is evaluated the structure is missing: -data-list-register-values --thread 1 --frame 0 --skip-unavailable r 57 ^done,register-values=[{number="57",value="0x00000000000000000000000000000000"}] Please provide the structure for ymm{N}h registers as well, so that one can to inspect parts of the register's value. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2023-05-15 7:02 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-30445-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).