From: Milica Matic <milica.matic@htecgroup.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Milica Matic <milica.matic@htecgroup.com>,
Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
Milos Kalicanin <milos.kalicanin@htecgroup.com>,
"simark@simark.ca" <simark@simark.ca>,
"cfu@wavecomp.com" <cfu@wavecomp.com>,
"aburgess@redhat.com" <aburgess@redhat.com>,
"kevinb@redhat.com" <kevinb@redhat.com>,
"macro@orcam.me.uk" <macro@orcam.me.uk>
Subject: [PATCH 0/2] gdb: mips: Add MIPSR6 support
Date: Wed, 19 Feb 2025 13:01:32 +0000 [thread overview]
Message-ID: <20250219130125.356900-1-milica.matic@htecgroup.com> (raw)
Introduce new instruction encodings from Release 6 of the MIPS
architecture [1]. Support breakpoints and single stepping with
compact branches, forbidden slots, new branch instruction and
new atomic load-store instruction encodings.
Changes from v11: Splitting the patch into two parts: Formatting the
mips-tdep.c file and "gdb: mips: Add MIPSR6 support".
[1] "MIPS64 Architecture for Programmers Volume II-A: The MIPS64
Instruction Set Reference Manual", Document Number: MD00087,
Revision 6.06, December 15, 2016, Section 3 "The MIPS64
Instruction Set", pp. 42-530
https://s3-eu-west-1.amazonaws.com/downloads-mips/documents/\
MD00087-2B-MIPS64BIS-AFP-6.06.pdf
2025-02-19
Andrew Bennett <andrew.bennett@imgtec.com>
Matthew Fortune <matthew.fortune@mips.com>
Faraz Shahbazker <fshahbazker@wavecomp.com>
next reply other threads:[~2025-02-19 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 13:01 Milica Matic [this message]
2025-02-19 13:01 ` [PATCH v12 " Milica Matic
2025-02-19 13:01 ` [PATCH v12 1/2] Apply coding guidelines Milica Matic
2025-02-19 23:21 ` Kevin Buettner
2025-02-23 16:40 ` Maciej W. Rozycki
2025-02-19 13:01 ` [PATCH v12 2/2] gdb: mips: Add MIPSR6 support Milica Matic
2025-02-25 22:35 ` Maciej W. Rozycki
2025-03-02 0:17 ` Maciej W. Rozycki
2025-03-28 17:09 ` Maciej W. Rozycki
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=20250219130125.356900-1-milica.matic@htecgroup.com \
--to=milica.matic@htecgroup.com \
--cc=Djordje.Todorovic@htecgroup.com \
--cc=aburgess@redhat.com \
--cc=cfu@wavecomp.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=macro@orcam.me.uk \
--cc=milos.kalicanin@htecgroup.com \
--cc=simark@simark.ca \
/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