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/28504] FAIL: gdb.arch/i386-sse.exp: check contents of data[2]
Date: Mon, 22 Nov 2021 11:43:37 +0000	[thread overview]
Message-ID: <bug-28504-4717-G6PsvqiTPa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28504-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28504

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Hit this again, on a different machine:
...
Linux cloud113 5.15.2-1-default #1 SMP Sat Nov 13 14:10:12 UTC 2021 (26a203b)
x86_64 x86_64 x86_64 GNU/Linux^M
...

Same cpu though:
...
model name      : Intel(R) Xeon(R) CPU           E5506  @ 2.13GHz^M
...

I've also added an extra check, after the register set to verify the register
contents.  I've also enabled some debug prints, so we got:
...
(gdb) PASS: gdb.arch/i386-sse.exp: check float contents of %xmm1 after add
set var $xmm2.v4_float[0] = 2 + 10^M
-> multi-thread->log_command (...)^M
<- multi-thread->log_command (set var $xmm2.v4_float[0] = 2 + 10)^M
-> multi-thread->thread_address_space (...)^M
<- multi-thread->thread_address_space (23546) = 1^M
-> multi-thread->thread_address_space (...)^M
<- multi-thread->thread_address_space (23546) = 1^M
-> multi-thread->prepare_to_store (...)^M
<- multi-thread->prepare_to_store (0x55fb8deb8ae0)^M
-> multi-thread->store_registers (...)^M
<- multi-thread->store_registers (0x55fb8deb8ae0, 42)^M
target_store_registers (xmm2) = 00004041000000000000000000000000^M
-> multi-thread->thread_architecture (...)^M
<- multi-thread->thread_architecture (23546) = i386:x86-64^M
-> multi-thread->thread_address_space (...)^M
<- multi-thread->thread_address_space (23546) = 1^M
-> multi-thread->get_unwinder (...)^M
<- multi-thread->get_unwinder () = 0x0^M
-> multi-thread->get_tailcall_unwinder (...)^M
<- multi-thread->get_tailcall_unwinder () = 0x0^M
-> multi-thread->thread_address_space (...)^M
<- multi-thread->thread_address_space (23546) = 1^M
-> multi-thread->fetch_registers (...)^M
<- multi-thread->fetch_registers (0x55fb8deb8ae0, 16)^M
target_fetch_registers (rip) = 5316400000000000 0x401653 4200019^M
multi-thread:target_xfer_partial (3, (null), 0x55fb8e0cfc80, 0x0,
0x7fffffffd6e8, 8) = 1, 8, bytes =^M
 c0 d5 dc f7 ff 7f 00 00^M
(gdb) PASS: gdb.arch/i386-sse.exp: set %xmm2
print $xmm2.v4_float^M
-> multi-thread->log_command (...)^M
<- multi-thread->log_command (print $xmm2.v4_float)^M
-> multi-thread->thread_address_space (...)^M
<- multi-thread->thread_address_space (23546) = 1^M
-> multi-thread->fetch_registers (...)^M
<- multi-thread->fetch_registers (0x55fb8deb8ae0, 42)^M
target_fetch_registers (xmm2) = 00000000000000000000000000000000^M
-> multi-thread->supports_memory_tagging (...)^M
<- multi-thread->supports_memory_tagging () = false^M
$36 = {0, 0, 0, 0}^M
(gdb) FAIL: gdb.arch/i386-sse.exp: check float contents of %xmm2 after add
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2021-11-22 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 12:02 [Bug testsuite/28504] New: " vries at gcc dot gnu.org
2021-10-27 13:01 ` [Bug testsuite/28504] " vries at gcc dot gnu.org
2021-11-18 11:38 ` vries at gcc dot gnu.org
2021-11-22 11:43 ` vries at gcc dot gnu.org [this message]

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-28504-4717-G6PsvqiTPa@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).