From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 0/3] Ravenscar simplification + FPU feature
Date: Tue, 14 Jun 2022 09:08:17 -0600 [thread overview]
Message-ID: <87pmjbxoym.fsf@tromey.com> (raw)
In-Reply-To: <20220531125731.1280943-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Tue, 31 May 2022 06:57:28 -0600")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> This series simplifies the Ravenscar layer in gdb, making it more
Tom> table-based and not code-based. It also fixes a bug, and adds support
Tom> for a missing feature -- some Ravenscar targets manage the FPU state
Tom> on demand, and so the runtime has to be queried to decide where to
Tom> find FP registers.
Tom> Tested using the internal AdaCore test suite. I've never gotten cross
Tom> testing working using qemu with the gdb test suite, and would
Tom> Ravenscar need extra setup on top of that.
I'm checking these in now.
Tom
prev parent reply other threads:[~2022-06-14 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 12:57 Tom Tromey
2022-05-31 12:57 ` [PATCH 1/3] Fix bugs in aarch64-ravenscar-thread.c Tom Tromey
2022-05-31 12:57 ` [PATCH 2/3] Reimplement ravenscar registers using tables Tom Tromey
2022-05-31 12:57 ` [PATCH 3/3] Implement lazy FPU initialization for ravenscar Tom Tromey
2022-06-14 15:08 ` Tom Tromey [this message]
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=87pmjbxoym.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@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).