From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3BD653858C60; Fri, 3 Feb 2023 09:26:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3BD653858C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675416370; bh=c9cbv9xtfexjHFnqOZXru9K8Uw7mZc6ajZ7SjQHP/c0=; h=From:To:Subject:Date:From; b=j5wo17ARdOo6le1P5xhzozHD3OxzL8gw2/wVNQmTPCviaRMPbxHAPR42BbNNUH0Nz nSYhpKltD42BOLueY+Lcg8zfAcl/pP35QkbQlO1Dx0oLC2N15/BwBPUHSQgpPIhvtF 06aWx5BQXv9aRGm241ViOBE28HtRUvh6u3MdY57I= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug record/30073] New: [intel Efficient-core] FAIL: gdb.btrace/exception.exp: flat (pattern 1) Date: Fri, 03 Feb 2023 09:26:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org 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=3D30073 Bug ID: 30073 Summary: [intel Efficient-core] FAIL: gdb.btrace/exception.exp: flat (pattern 1) Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- I got a new laptop, build gdb and ran the gdb testsuite, and ran into: ... (gdb) PASS: gdb.btrace/exception.exp: continue to breakpoint: cont to bp.2 gdb_expect_list pattern: /1 main\(\)^M 2 test\(\)^M 3 foo\(\)^M 4 bar\(\)^M 5 bad\(\)^M/ record function-call-history 1^M 1 main()^M (gdb) FAIL: gdb.btrace/exception.exp: flat (pattern 1) ... I could reproduce it sometimes, but not all the time, till I tried out using taskset. When using: - taskset -c 0-3, the test-case passes.=20=20 - taskset -c 4-11, the test-case fails. The processor is a i7-1250U with 12 threads: - 2 performance cores (I guess providing 2 threads per core), and - 8 efficient cores. So, I guess somehow it doesn't run properly on efficient cores. --=20 You are receiving this mail because: You are on the CC list for the bug.=