From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 247773858C2B; Fri, 1 Sep 2023 14:39:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 247773858C2B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1693579162; bh=IND0cj4jb90oDMdxu4eK3fHWOq/vVhOsIVhO+aSP6aE=; h=From:To:Subject:Date:From; b=iFV1TA2hX9UOJlqeQPZmv3MhKF6xskSiTCO6vatFqag7fK4pHzzNi7KRnyCnIROja dBW5aVX+/JgTFOkpY53htaY7lgE5T19tIHmBuTozM5Jb85KVNPNSq01zDtd7ZH8jOH XB9lzHmFABlgk6KIMvQyJphCgxJ0OFs3WXMjIqrw= From: "simon.marchi at polymtl dot ca" To: gdb-prs@sourceware.org Subject: [Bug gdb/30818] New: GDB + GDBserver doesn't set AVX512 registers properly Date: Fri, 01 Sep 2023 14:39:21 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at polymtl dot ca X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30818 Bug ID: 30818 Summary: GDB + GDBserver doesn't set AVX512 registers properly Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: simon.marchi at polymtl dot ca Target Milestone: --- On a machine with AVX512 support (AMD EPYC 9634), I see: $ make check TESTS=3D"gdb.arch/i386-avx512.exp" RUNTESTFLAGS=3D"--target_board=3Dnative-gdbserver" ... FAIL: gdb.arch/i386-avx512.exp: check contents of zmm_data[16] after writing ZMM regs ... I can reproduce more simply with (after connecting to gdbserver): (gdb) print $zmm16.v8_int64=20 $1 =3D {0, 0, 0, 0, 0, 0, 0, 0} (gdb) print $zmm16.v8_int64 =3D {11,22,33,44,55,66,77,88} $2 =3D {11, 22, 33, 44, 55, 66, 77, 88} (gdb) print $zmm16.v8_int64 $3 =3D {11, 22, 33, 44, 55, 66, 77, 88} (gdb) step 5 ++x; (gdb) print $zmm16.v8_int64 $4 =3D {11, 22, 77, 88, 0, 0, 0, 0} It looks like writing to the local regcache in GDB worked fine, but the writeback to gdbserver didn't work fine. --=20 You are receiving this mail because: You are on the CC list for the bug.=