[gcc(refs/users/marxin/heads/marxin-gcc-benchmark-branch)] config.gcc <obsolete targets>: Add crisv32-*-* and cris-*-linux*
Martin Liska
marxin@gcc.gnu.org
Mon Mar 30 10:15:06 GMT 2020
https://gcc.gnu.org/g:8118184c3e144cb6455caca0b19541cb317061a4
commit 8118184c3e144cb6455caca0b19541cb317061a4
Author: Hans-Peter Nilsson <hp@axis.com>
Date: Sat Jan 18 14:23:59 2020 +0100
config.gcc <obsolete targets>: Add crisv32-*-* and cris-*-linux*
I'm sorry to say that there's no incentive to maintain
crisv32-*-* and cris-*-linux* configurations beyond nostalgia,
(and I'm out of that for the moment). Support in the Linux
kernel for either applicable CRIS variant (CRIS v10 and CRIS
v32) is gone since 2018. Their related part of the cc0
transition workload would be noticable. Note that cris-elf
remains, but crisv32-elf and the CRIS v32 multilib will be
removed, at least for now.
I'm not completely happy about the message (the next-next line
after the context) "*** unless a maintainer comes forward"
because it'd have to be at an infinitesimal maintenance cost to
the cris-elf support. Still, I'm not bothered enough to add
another case construct or means for "planned obsolescence".
Diff:
---
gcc/ChangeLog | 4 ++++
gcc/config.gcc | 2 ++
2 files changed, 6 insertions(+)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 6f05cdbbba4..173f62d814a 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2020-01-18 Hans-Peter Nilsson <hp@axis.com>
+
+ * config.gcc <obsolete targets>: Add crisv32-*-* and cris-*-linux*
+
2019-01-18 Gerald Pfeifer <gerald@pfeifer.com>
* varpool.c (ctor_useable_for_folding_p): Fix grammar.
diff --git a/gcc/config.gcc b/gcc/config.gcc
index 5a2f1730477..5532a7be6ac 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -248,6 +248,8 @@ md_file=
# Obsolete configurations.
case ${target} in
tile*-*-* \
+ | crisv32-*-* \
+ | cris-*-linux* \
)
if test "x$enable_obsolete" != xyes; then
echo "*** Configuration ${target} is obsolete." >&2
More information about the Gcc-cvs
mailing list