public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29743] [gdb/tdep, powerpc64le] FAIL: gdb.arch/powerpc-power10.exp: found: pmxvbf16ger2 a4,vs0,vs1,0,0,0
Date: Fri, 04 Nov 2022 16:34:09 +0000 [thread overview]
Message-ID: <bug-29743-4717-XoZBoNQ4gd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29743-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29743
--- Comment #2 from Carl E Love <cel at us dot ibm.com> ---
The two patches were approved and committed.
commit 49977100a1c9940ee8639fc1feb8bc39839a8c93
Author: Carl Love <cel@us.ibm.com>
Date: Fri Nov 4 12:13:52 2022 -0400
PowerPC fix for the gdb.arch/powerpc-power10.exp test.
commit 45830439cef3c827ae5ddb3915a1edcf1206dc77 (HEAD -> master, origin/master,
origin/HEAD)
Author: Carl Love <cel@us.ibm.com>
Date: Fri Nov 4 12:14:01 2022 -0400
PowerPC update comments for the MMA instruction name changes.
I think the issue can be closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-04 16:34 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 [this message]
2022-11-05 7:38 ` [Bug testsuite/29743] [gdb/testsuite, " 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-29743-4717-XoZBoNQ4gd@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).