From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Convert py-arch.c to "safety" approach
Date: Fri, 16 Oct 2026 10:18:55 -0600 [thread overview]
Message-ID: <87bj8thb4g.fsf@tromey.com> (raw)
In-Reply-To: <20260808182339.3936136-1-tom@tromey.com> (Tom Tromey's message of "Sat, 8 Aug 2026 12:23:39 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This patch converts py-arch.c to the new Python safety approach. A
Tom> few changes outside this file were also needed: some updates to
Tom> py-register.c (changing some functions that are only called from
Tom> py-arch.c), the new noargs_function template, and the use of a wrapper
Tom> in python.c.
Tom> Regression tested on x86-64 Fedora 40.
I've rebased and retested this.
I'm checking it in now.
Tom
prev parent reply other threads:[~2026-10-16 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 18:23 Tom Tromey
2026-10-16 16:18 ` 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=87bj8thb4g.fsf@tromey.com \
--to=tom@tromey.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