public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30912] Regression: make check TESTS="gdb.base/gcore.exp" RUNTESTFLAGS="--target_board=native-extended-gdbserver"
Date: Sat, 28 Oct 2023 19:36:29 +0000 [thread overview]
Message-ID: <bug-30912-4717-3012oLLbtE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30912-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30912
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #4 from Simon Marchi <simark at simark dot ca> ---
IIRC, this failure was introduced with the XSAVE work, but I don't remember the
specifics of why the test passed before and it doesn't now. It's likely
related to the fact that we don't have a way for GDB to get the CPUID
information from GDBserver (John can confirm).
Looking at the failure a bit more in details, when doing "info all-reg" we
expect this (I only included ymm0 for brevity, but it's ymm0 to ymm15):
ymm0 {v16_bfloat16 = {0xc300, 0xf7e9, 0x7fff, 0x0, 0xc300, 0xf7e9,
0x7fff, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v16_half = {0xc300,
0xf7e9, 0x7fff, 0x0, 0xc300, 0xf7e9, 0x7fff, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
0x0, 0x0}, v8_float = {0xf7e9c300, 0x7fff, 0xf7e9c300, 0x7fff, 0x0, 0x0, 0x0,
0x0}, v4_double = {0x7ffff7e9c300, 0x7ffff7e9c300, 0x0, 0x0}, v32_int8 = {0x0,
0xc3, 0xe9, 0xf7, 0xff, 0x7f, 0x0, 0x0, 0x0, 0xc3, 0xe9, 0xf7, 0xff, 0x7f, 0x0
<repeats 18 times>}, v16_int16 = {0xc300, 0xf7e9, 0x7fff, 0x0, 0xc300, 0xf7e9,
0x7fff, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v8_int32 = {0xf7e9c300,
0x7fff, 0xf7e9c300, 0x7fff, 0x0, 0x0, 0x0, 0x0}, v4_int64 = {0x7ffff7e9c300,
0x7ffff7e9c300, 0x0, 0x0}, v2_int128 = {0x7ffff7e9c30000007ffff7e9c300, 0x0}}
but get:
ymm0 {v16_bfloat16 = {0xc300, 0xf7e9, 0x7fff, 0x0, 0xc300, 0xf7e9,
0x7fff, 0x0, <unavailable>, <unavailable>, <unavailable>, <unavailable>,
<unavailable>, <unavailable>, <unavailable>, <unavailable>}, v16_half =
{0xc300, 0xf7e9, 0x7fff, 0x0, 0xc300, 0xf7e9, 0x7fff, 0x0, <unavailable>,
<unavailable>, <unavailable>, <unavailable>, <unavailable>, <unavailable>,
<unavailable>, <unavailable>}, v8_float = {0xf7e9c300, 0x7fff, 0xf7e9c300,
0x7fff, <unavailable>, <unavailable>, <unavailable>, <unavailable>}, v4_double
= {0x7ffff7e9c300, 0x7ffff7e9c300, <unavailable>, <unavailable>}, v32_int8 =
{0x0, 0xc3, 0xe9, 0xf7, 0xff, 0x7f, 0x0, 0x0, 0x0, 0xc3, 0xe9, 0xf7, 0xff,
0x7f, 0x0, 0x0, <unavailable> <repeats 16 times>}, v16_int16 = {0xc300, 0xf7e9,
0x7fff, 0x0, 0xc300, 0xf7e9, 0x7fff, 0x0, <unavailable>, <unavailable>,
<unavailable>, <unavailable>, <unavailable>, <unavailable>, <unavailable>,
<unavailable>}, v8_int32 = {0xf7e9c300, 0x7fff, 0xf7e9c300, 0x7fff,
<unavailable>, <unavailable>, <unavailable>, <unavailable>}, v4_int64 =
{0x7ffff7e9c300, 0x7ffff7e9c300, <unavailable>, <unavailable>}, v2_int128 =
{0x7ffff7e9c30000007ffff7e9c300, <unavailable>}}
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-28 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 16:53 [Bug gdb/30912] New: " simon.marchi at polymtl dot ca
2023-09-28 17:40 ` [Bug gdb/30912] " brobecker at gnat dot com
2023-09-28 18:45 ` brobecker at gnat dot com
2023-10-28 15:54 ` brobecker at gnat dot com
2023-10-28 19:36 ` simark at simark dot ca [this message]
2023-11-20 23:59 ` jhb at FreeBSD dot org
2023-11-22 20:56 ` jhb at FreeBSD dot org
2023-11-27 21:53 ` cvs-commit at gcc dot gnu.org
2023-11-27 22:00 ` cvs-commit at gcc dot gnu.org
2023-11-27 22:01 ` jhb at FreeBSD dot 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-30912-4717-3012oLLbtE@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).