From 8118184c3e144cb6455caca0b19541cb317061a4 Mon Sep 17 00:00:00 2001
From: Hans-Peter Nilsson <hp@axis.com>
Date: Sat, 18 Jan 2020 14:23:59 +0100
Subject: [PATCH] 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".
---
gcc/ChangeLog | 4 ++++
gcc/config.gcc | 2 ++
2 files changed, 6 insertions(+)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 6f05cdbbba49..173f62d814ac 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 5a2f17304773..5532a7be6ac7 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