From: John Baldwin <jhb@FreeBSD.org>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] i386-fbsd-nat: Assume PT_GETXMMREGS is present.
Date: Tue, 1 Mar 2022 10:25:18 -0800 [thread overview]
Message-ID: <50bc80e8-3934-9585-3204-6ba4b0821986@FreeBSD.org> (raw)
In-Reply-To: <51a3d32c-7ea2-a814-9716-af2fd478b70c@polymtl.ca>
On 3/1/22 6:22 AM, Simon Marchi wrote:
>
>
> On 2022-02-28 17:35, John Baldwin wrote:
>> PT_GETXMMREGS was first added in FreeBSD 6.0 released in November 2005.
>> The last FreeBSD release without support was 5.5 released in May 2006.
>> ---
>> gdb/i386-fbsd-nat.c | 14 --------------
>> 1 file changed, 14 deletions(-)
>>
>> diff --git a/gdb/i386-fbsd-nat.c b/gdb/i386-fbsd-nat.c
>> index 6fb67434a2d..a6ced66250c 100644
>> --- a/gdb/i386-fbsd-nat.c
>> +++ b/gdb/i386-fbsd-nat.c
>> @@ -42,9 +42,7 @@ class i386_fbsd_nat_target final
>> void fetch_registers (struct regcache *, int) override;
>> void store_registers (struct regcache *, int) override;
>>
>> -#if defined(PT_GETXMMREGS) || defined(PT_GETXSTATE_INFO)
>> const struct target_desc *read_description () override;
>> -#endif
>>
>> void resume (ptid_t, int, enum gdb_signal) override;
>>
>> @@ -59,9 +57,7 @@ static i386_fbsd_nat_target the_i386_fbsd_nat_target;
>> static size_t xsave_len;
>> #endif
>>
>> -#ifdef HAVE_PT_GETXMMREGS
>> static int have_ptrace_xmmregs;
>
> Is this variable (have_ptrace_xmmregs) still relevant? In other words,
> can the PT_GETXMMREGS request legitimately fail?
Yes, while the ptrace op always exists, it only works if the running CPU supports
SSE (and this is true in i386-bsd-nat.c as well). Granted, the number of systems
running modern BSD operating systems on a CPU that doesn't include SSE support
(think Pentium or Pentium Pro class CPUs) may be vanishingly small to the point
of zero.
--
John Baldwin
next prev parent reply other threads:[~2022-03-01 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 22:35 [PATCH 0/3] Assume PT_GETXMMREGS is always present on *BSD/i386 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 [this message]
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 ` [PATCH 0/3] Assume PT_GETXMMREGS is always present on *BSD/i386 Tom Tromey
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=50bc80e8-3934-9585-3204-6ba4b0821986@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).