From: Tom Tromey <tom@tromey.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Assume PT_GETXMMREGS is always present on *BSD/i386
Date: Tue, 01 Mar 2022 13:48:36 -0700 [thread overview]
Message-ID: <87o82pjt5n.fsf@tromey.com> (raw)
In-Reply-To: <20220228223539.93563-1-jhb@FreeBSD.org> (John Baldwin's message of "Mon, 28 Feb 2022 14:35:36 -0800")
>>>>> "John" == John Baldwin <jhb@FreeBSD.org> writes:
John> All of the BSD operating systems have included support for the XMM
John> register set for SSE since at least mid 2006. This patch series
John> assumes it is present to reduce #ifdef's and remove a
John> no-longer-necessary configure check.
FWIW, I skimmed these and they all seem fine to me.
Tom
prev parent reply other threads:[~2022-03-01 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 22:35 John Baldwin
2022-02-28 22:35 ` [PATCH 1/3] i386-fbsd-nat: Assume PT_GETXMMREGS is present John Baldwin
2022-03-01 14:22 ` Simon Marchi
2022-03-01 18:25 ` John Baldwin
2022-02-28 22:35 ` [PATCH 2/3] i386-bsd-nat: " John Baldwin
2022-02-28 22:35 ` [PATCH 3/3] configure: Stop checking for PT_GETXMMREGS John Baldwin
2022-03-01 20:48 ` 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=87o82pjt5n.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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).