From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 3/3] configure: Stop checking for PT_GETXMMREGS.
Date: Mon, 28 Feb 2022 14:35:39 -0800 [thread overview]
Message-ID: <20220228223539.93563-4-jhb@FreeBSD.org> (raw)
In-Reply-To: <20220228223539.93563-1-jhb@FreeBSD.org>
This request is present on all modern *BSD/i386 systems (those
released since mid-2006), and the *BSD/i386 targets now assume it is
present unconditionally.
---
gdb/configure | 37 -------------------------------------
gdb/configure.ac | 20 --------------------
2 files changed, 57 deletions(-)
diff --git a/gdb/configure b/gdb/configure
index 425bdb08a73..b34baff13be 100755
--- a/gdb/configure
+++ b/gdb/configure
@@ -16245,43 +16245,6 @@ $as_echo "#define HAVE_PT_GETDBREGS 1" >>confdefs.h
fi
-# See if <sys/ptrace.h> provides the PT_GETXMMREGS request.
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for PT_GETXMMREGS" >&5
-$as_echo_n "checking for PT_GETXMMREGS... " >&6; }
-if ${gdb_cv_have_pt_getxmmregs+:} false; then :
- $as_echo_n "(cached) " >&6
-else
- cat confdefs.h - <<_ACEOF >conftest.$ac_ext
-/* end confdefs.h. */
-#include <sys/types.h>
- #include <sys/ptrace.h>
-int
-main ()
-{
-PT_GETXMMREGS;
-
- ;
- return 0;
-}
-_ACEOF
-if ac_fn_c_try_compile "$LINENO"; then :
- gdb_cv_have_pt_getxmmregs=yes
-else
- gdb_cv_have_pt_getxmmregs=no
-
-fi
-rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
-
-fi
-
-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $gdb_cv_have_pt_getxmmregs" >&5
-$as_echo "$gdb_cv_have_pt_getxmmregs" >&6; }
-if test "$gdb_cv_have_pt_getxmmregs" = yes; then
-
-$as_echo "#define HAVE_PT_GETXMMREGS 1" >>confdefs.h
-
-fi
-
# See if <sys/ptrace.h> supports LWP names on FreeBSD
# Older FreeBSD versions don't have the pl_tdname member of
# `struct ptrace_lwpinfo'.
diff --git a/gdb/configure.ac b/gdb/configure.ac
index c6fa19b20bc..bc8925ddd69 100644
--- a/gdb/configure.ac
+++ b/gdb/configure.ac
@@ -1486,26 +1486,6 @@ if test "$gdb_cv_have_pt_getdbregs" = yes; then
[Define if sys/ptrace.h defines the PT_GETDBREGS request.])
fi
-# See if <sys/ptrace.h> provides the PT_GETXMMREGS request.
-AC_MSG_CHECKING(for PT_GETXMMREGS)
-AC_CACHE_VAL(
- [gdb_cv_have_pt_getxmmregs],
- [AC_COMPILE_IFELSE(
- [AC_LANG_PROGRAM(
- [#include <sys/types.h>
- #include <sys/ptrace.h>],
- [PT_GETXMMREGS;]
- )],
- [gdb_cv_have_pt_getxmmregs=yes],
- [gdb_cv_have_pt_getxmmregs=no]
- )]
-)
-AC_MSG_RESULT($gdb_cv_have_pt_getxmmregs)
-if test "$gdb_cv_have_pt_getxmmregs" = yes; then
- AC_DEFINE(HAVE_PT_GETXMMREGS, 1,
- [Define if sys/ptrace.h defines the PT_GETXMMREGS request.])
-fi
-
# See if <sys/ptrace.h> supports LWP names on FreeBSD
# Older FreeBSD versions don't have the pl_tdname member of
# `struct ptrace_lwpinfo'.
--
2.34.1
next prev parent reply other threads:[~2022-02-28 22:35 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
2022-02-28 22:35 ` [PATCH 2/3] i386-bsd-nat: " John Baldwin
2022-02-28 22:35 ` John Baldwin [this message]
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=20220228223539.93563-4-jhb@FreeBSD.org \
--to=jhb@freebsd.org \
--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).