From: Enze Li <enze.li@hotmail.com>
To: gdb-patches@sourceware.org
Cc: enze.li@gmx.com
Subject: [PATCH] gdb: remove gdb_indent.sh
Date: Wed, 1 Feb 2023 22:37:41 +0800 [thread overview]
Message-ID: <OS3P286MB2152EEC03912301D0BA5F7DEF0D19@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (raw)
GDB has been converted to a C++ program for many years[1], and the
gdb_indent.sh will not be used any more. Therefore, remove the script as
obvious.
[1] https://sourceware.org/gdb/wiki/cxx-conversion
---
gdb/gdb_indent.sh | 92 -----------------------------------------------
1 file changed, 92 deletions(-)
delete mode 100755 gdb/gdb_indent.sh
diff --git a/gdb/gdb_indent.sh b/gdb/gdb_indent.sh
deleted file mode 100755
index 115b99521fc..00000000000
--- a/gdb/gdb_indent.sh
+++ /dev/null
@@ -1,92 +0,0 @@
-#!/bin/sh
-
-# Try to find a GNU indent. There could be a BSD indent in front of a
-# GNU gindent so when indent is found, keep looking.
-
-# Make certain that the script is not running in an internationalized
-# environment.
-LANG=c ; export LANG
-LC_ALL=c ; export LC_ALL
-
-gindent=
-indent=
-paths=`echo $PATH | sed \
- -e 's/::/:.:/g' \
- -e 's/^:/.:/' \
- -e 's/:$/:./' \
- -e 's/:/ /g'`
-for path in $paths
-do
- if test ! -n "${gindent}" -a -x ${path}/gindent
- then
- gindent=${path}/gindent
- break
- elif test ! -n "${indent}" -a -x ${path}/indent
- then
- indent=${path}/indent
- fi
-done
-
-if test -n "${gindent}"
-then
- indent=${gindent}
-elif test -n "${indent}"
-then
- :
-else
- echo "Indent not found" 1>&2
-fi
-
-
-# Check that the indent found is both GNU and a reasonable version.
-# Different indent versions give different indentation.
-
-m1=2
-m2=2
-m3=9
-
-version=`${indent} --version 2>/dev/null < /dev/null`
-case "${version}" in
- *GNU* ) ;;
- * ) echo "error: GNU indent $m1.$m2.$m3 expected" 1>&2 ; exit 1;;
-esac
-v1=`echo "${version}" | sed 's/^.* \([0-9]*\)\.\([0-9]*\)\.\([0-9]*\)$/\1/'`
-v2=`echo "${version}" | sed 's/^.* \([0-9]*\)\.\([0-9]*\)\.\([0-9]*\)$/\2/'`
-v3=`echo "${version}" | sed 's/^.* \([0-9]*\)\.\([0-9]*\)\.\([0-9]*\)$/\3/'`
-
-if test $m1 -ne $v1 -o $m2 -ne $v2 -o $m3 -gt $v3
-then
- echo "error: Must be GNU indent version $m1.$m2.$m3 or later" 1>&2
- exit 1
-fi
-
-if test $m3 -ne $v3
-then
- echo "warning: GNU indent version $m1.$m2.$m3 recommended" 1>&2
-fi
-
-# Check that we're in the GDB source directory
-
-case `pwd` in
- */gdb ) ;;
- */sim/* ) ;;
- * ) echo "Not in GDB directory" 1>&2 ; exit 1 ;;
-esac
-
-
-# Run indent per GDB specs
-
-types="\
--T FILE \
--T bfd -T asection -T pid_t \
--T prgregset_t -T fpregset_t -T gregset_t -T sigset_t \
--T td_thrhandle_t -T td_event_msg_t -T td_thr_events_t \
--T td_notify_t -T td_thr_iter_f -T td_thrinfo_t \
--T caddr_t \
-`cat *.h | sed -n \
- -e 's/^.*[^a-z0-9_]\([a-z0-9_]*_ftype\).*$/-T \1/p' \
- -e 's/^.*[^a-z0-9_]\([a-z0-9_]*_func\).*$/-T \1/p' \
- -e 's/^typedef.*[^a-zA-Z0-9_]\([a-zA-Z0-9_]*[a-zA-Z0-9_]\);$/-T \1/p' \
- | sort -u`"
-
-${indent} ${types} "$@"
base-commit: 4788abdec79a937e51ad334b608fa1bd03713112
--
2.39.1
next reply other threads:[~2023-02-01 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 14:37 Enze Li [this message]
2023-02-01 16:26 ` Simon Marchi
2023-02-02 13:01 ` Enze Li
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=OS3P286MB2152EEC03912301D0BA5F7DEF0D19@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM \
--to=enze.li@hotmail.com \
--cc=enze.li@gmx.com \
--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).