public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug record/30075] [intel Performance-core] FAIL: gdb.python/py-record-btrace.exp: prepare record: python insn = r.instruction_history Date: Tue, 14 Feb 2023 12:15:54 +0000 [thread overview] Message-ID: <bug-30075-4717-BNGjVuOmsk@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30075-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30075 --- Comment #10 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5bed9dc992a0136d403a7addb29a2ed822fd4fd2 commit 5bed9dc992a0136d403a7addb29a2ed822fd4fd2 Author: Tom de Vries <tdevries@suse.de> Date: Tue Feb 14 13:15:49 2023 +0100 [gdb/testsuite] Add xfail in gdb.python/py-record-btrace.exp There's a HW bug affecting Processor Trace on some Intel processors (Ice Lake to Raptor Lake microarchitectures). The bug was exposed by linux kernel commit 670638477aed ("perf/x86/intel/pt: Opportunistically use single range output mode"), added in version v5.5.0, and was worked around by commit ce0d998be927 ("perf/x86/intel/pt: Fix sampling using single range output") in version 6.1.0. The bug manifests (on a Performance-core of an i7-1250U, an Alder Lake cpu) in a single test-case: ... (gdb) python insn = r.instruction_history^M warning: Decode error (-20) at instruction 33 (offset = 0x3d6a, \ pc = 0x400501): compressed return without call.^M (gdb) FAIL: gdb.python/py-record-btrace.exp: prepare record: \ python insn = r.instruction_history ... Add a corresponding XFAIL. Note that the i7-1250U has both Performance-cores and Efficient-cores, and on an Efficient-Core the test-case runs without any problems, so if the testsuite run is not pinned to a specific cpu, the test may either PASS or XFAIL. Tested on x86_64-linux: - openSUSE Leap 15.4 with linux kernel version 5.14.21 - openSUSE Tumbleweed with linux kernel version 6.1.8 PR testsuite/30075 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30075 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-14 12:15 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-03 12:24 [Bug record/30075] New: " vries at gcc dot gnu.org 2023-02-04 20:13 ` [Bug record/30075] " vries at gcc dot gnu.org 2023-02-06 14:05 ` vries at gcc dot gnu.org 2023-02-06 15:02 ` vries at gcc dot gnu.org 2023-02-07 11:35 ` vries at gcc dot gnu.org 2023-02-07 12:03 ` vries at gcc dot gnu.org 2023-02-07 12:05 ` markus.t.metzger at intel dot com 2023-02-07 12:08 ` markus.t.metzger at intel dot com 2023-02-09 10:46 ` markus.t.metzger at intel dot com 2023-02-09 12:15 ` vries at gcc dot gnu.org 2023-02-13 18:10 ` vries at gcc dot gnu.org 2023-02-14 12:15 ` cvs-commit at gcc dot gnu.org [this message] 2023-02-14 12:16 ` [Bug testsuite/30075] " 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-30075-4717-BNGjVuOmsk@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).