public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "thiago.bauermann at linaro dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/31666] New: Support aarch64 mops feature ops ( CPYF*, CPY*, SET* and SETG*) Date: Mon, 22 Apr 2024 04:11:17 +0000 [thread overview] Message-ID: <bug-31666-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31666 Bug ID: 31666 Summary: Support aarch64 mops feature ops ( CPYF*, CPY*, SET* and SETG*) Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: thiago.bauermann at linaro dot org Target Milestone: --- Starting with Arm v8.8/v9.3, a new architectural feature (FEAT_MOPS) provides new instructions to perform memory copy and memory set operations in a standardized way. There are specialized versions of memcpy, memmove and memset using them in glibc 2.39. These instructions appear as a sequence of 3: one prologue, one main and one epilogue instruction. The AArch64 target of GDB needs two things to support them: 1. Recognize the trio of instructions as one atomic sequence. 2. Recognize the instructions for record/replay. Patches for both are being finalized and will be posted in the next few days. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-04-22 4:11 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-22 4:11 thiago.bauermann at linaro dot org [this message] 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
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@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).