From: Jovan Dmitrovic <jovan.dmitrovic@htecgroup.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
Milica Matic <milica.matic@htecgroup.com>,
"Maciej W . Rozycki" <macro@orcam.me.uk>,
Jovan Dmitrovic <jovan.dmitrovic@htecgroup.com>
Subject: [PATCH v13 0/2] gdb: mips: Add MIPSR6 support
Date: Wed, 4 Jun 2025 12:38:48 +0000 [thread overview]
Message-ID: <20250604123838.501596-1-jovan.dmitrovic@htecgroup.com> (raw)
Hello,
I made some changes to Milica's v12, considering the mips-64-r6.c
couldn't compile (thanks Maciej for bringing this to our attention).
I've used the standard_testfile procedure, considering that seems to
be the way to go for properly setting up the necessary testfile values,
so that the problem of the missing directory doesn't occur.
Regards,
Jovan
---
Milica Matic (2):
Apply coding guidelines
gdb: mips: Add MIPSR6 support
gdb/mips-tdep.c | 861 +++++++++++++++++++-----
gdb/testsuite/gdb.arch/mips-64-r6.c | 916 ++++++++++++++++++++++++++
gdb/testsuite/gdb.arch/mips-64-r6.exp | 74 +++
3 files changed, 1679 insertions(+), 172 deletions(-)
create mode 100644 gdb/testsuite/gdb.arch/mips-64-r6.c
create mode 100644 gdb/testsuite/gdb.arch/mips-64-r6.exp
--
2.34.1
next reply other threads:[~2025-06-04 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 12:38 Jovan Dmitrovic [this message]
2025-06-04 12:39 ` [PATCH v13 1/2] gdb: mips: Apply coding guidelines Jovan Dmitrovic
2026-09-17 11:21 ` Maciej W. Rozycki
2025-06-04 12:39 ` [PATCH v13 2/2] gdb: mips: Add MIPSR6 support Jovan Dmitrovic
2026-09-17 11:22 ` 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=20250604123838.501596-1-jovan.dmitrovic@htecgroup.com \
--to=jovan.dmitrovic@htecgroup.com \
--cc=Djordje.Todorovic@htecgroup.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=milica.matic@htecgroup.com \
/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