From: Nick Clifton via Gdb <gdb@sourceware.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: RFC: Deprecate the ARM simulator
Date: Mon, 23 Sep 2024 14:31:07 +0100 [thread overview]
Message-ID: <c893d0df-1104-4c99-9194-acccb2252c4d@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hi Guys,
I would like to deprecate or even delete the ARM simulator.
Although I am listed as the maintainer for the sim, I have not
made any improvements to it for years and it is completely
unable to handle modern ARM cores. The only updates to the
sources in the last few years have been to fix compilation
issues, and basically it has bit-rotted away.
It is not entirely clear to me how a sim target should be
deprecated. I am attaching a patch that shows one possible
method - adding code to the sim/configure.ac file to indicate
that the target is deprecated. An alternative would be to
add the sim target to the noconfigdirs list that is constructed
in the top level configure.ac file. Although I think that
that list is for components that do not support the target at
all, rather than components where the target is deprecated.
Anyway, thoughts, comments, suggestions ?
Cheers
Nick
[-- Attachment #2: sim.configure.ac.patch --]
[-- Type: text/x-patch, Size: 834 bytes --]
diff --git a/sim/configure.ac b/sim/configure.ac
index fad5b71ee59..e9ec6e70efc 100644
--- a/sim/configure.ac
+++ b/sim/configure.ac
@@ -84,6 +84,18 @@ m4_define([SIM_TARGET], [dnl
AM_CONDITIONAL([SIM_ENABLE_ARCH_$2], [${sim_enable_arch_$2}])
])
+case $target in
+ arm*-*-* | \
+ null)
+ if test "x$enable_obsolete" != xyes; then
+ echo "*** Configuration $targ is obsolete." >&2
+ echo "*** Specify --enable-obsolete to build it anyway." >&2
+ echo "*** Support will be REMOVED in the next major release of GDB," >&2
+ echo "*** unless a maintainer comes forward." >&2
+ exit 1
+ fi;;
+esac
+
dnl WHEN ADDING ENTRIES TO THIS MATRIX:
dnl Make sure that the left side always has two dashes. Otherwise you can get
dnl spurious matches. Even for unambiguous cases, do this as a convention, else
next reply other threads:[~2024-09-23 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 13:31 Nick Clifton via Gdb [this message]
2024-09-23 16:17 ` Simon Marchi via Gdb
2024-09-23 16:34 ` Nick Clifton via Gdb
2024-09-23 16:45 ` Richard Earnshaw (lists) via Gdb
2024-09-24 11:03 ` Maciej W. Rozycki
2024-09-24 14:18 ` Nick Clifton via Gdb
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=c893d0df-1104-4c99-9194-acccb2252c4d@redhat.com \
--to=gdb@sourceware.org \
--cc=Richard.Earnshaw@arm.com \
--cc=nickc@redhat.com \
/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