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/29743] [gdb/testsuite, powerpc64le] FAIL: gdb.arch/powerpc-power10.exp: found: pmxvbf16ger2 a4,vs0,vs1,0,0,0 Date: Sat, 05 Nov 2022 07:38:06 +0000 [thread overview] Message-ID: <bug-29743-4717-exNDPIebue@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29743-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29743 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Component|tdep |testsuite Resolution|--- |FIXED Summary|[gdb/tdep, powerpc64le] |[gdb/testsuite, |FAIL: |powerpc64le] FAIL: |gdb.arch/powerpc-power10.ex |gdb.arch/powerpc-power10.ex |p: found: pmxvbf16ger2 |p: found: pmxvbf16ger2 |a4,vs0,vs1,0,0,0 |a4,vs0,vs1,0,0,0 Target Milestone|--- |13.1 --- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=49977100a1c9940ee8639fc1feb8bc39839a8c93 -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-11-05 7:38 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-02 18:33 [Bug tdep/29743] New: " vries at gcc dot gnu.org 2022-11-02 18:39 ` [Bug tdep/29743] " vries at gcc dot gnu.org 2022-11-02 18:42 ` [Bug tdep/29743] [gdb/tdep, powerpc64le] " vries at gcc dot gnu.org 2022-11-03 18:27 ` cel at us dot ibm.com 2022-11-04 16:34 ` cel at us dot ibm.com 2022-11-05 7:38 ` 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-29743-4717-exNDPIebue@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).