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 tdep/31666] Support aarch64 mops feature ops ( CPYF*, CPY*, SET* and SETG*)
Date: Fri, 07 Jun 2024 21:39:57 +0000	[thread overview]
Message-ID: <bug-31666-4717-xjkwj7lsMf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31666-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31666

--- Comment #4 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thiago Bauermann
<bauermann@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ebd06ca6b9bb2327e1269b52eb99b2f012faabf9

commit ebd06ca6b9bb2327e1269b52eb99b2f012faabf9
Author: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Date:   Sat Apr 20 23:18:26 2024 -0300

    gdb/aarch64: Add record support for MOPS instructions.

    There are two kinds of MOPS instructions: set instructions and copy
    instructions.  Within each group there are variants with minor
    differences in how they read or write to memory â e.g., non-temporal
    read and/or write, unprivileged read and/or write and permutations of
    those â but they work in the same way in terms of the registers and
    regions of memory that they modify.

    The new gdb.reverse/aarch64-mops.exp testcase verifies that MOPS
    instructions are recorded and correctly reversed.  Not all variants of the
    copy and set instructions are tested, since there are many and the record
    and replay target processes them in the same way.

    PR tdep/31666
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31666
    Approved-By: Luis Machado <luis.machado@arm.com>
    Tested-By: Luis Machado <luis.machado@arm.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-06-07 21:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22  4:11 [Bug tdep/31666] New: " thiago.bauermann at linaro dot org
2024-04-22  4:12 ` [Bug tdep/31666] " thiago.bauermann at linaro dot org
2024-05-04  0:09 ` thiago.bauermann at linaro dot org
2024-05-07  2:38 ` thiago.bauermann at linaro dot org
2024-06-07 21:39 ` cvs-commit at gcc dot gnu.org
2024-06-07 21:39 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-07 21:51 ` cvs-commit at gcc dot gnu.org
2024-06-07 21:51 ` cvs-commit at gcc dot gnu.org
2024-06-14 15:36 ` luis.machado at arm dot com
2024-06-14 16:13 ` thiago.bauermann at linaro dot org
2024-06-14 16:14 ` thiago.bauermann at linaro dot 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-31666-4717-xjkwj7lsMf@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).