From: Xi Ruoyao <xry111@xry111.site>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 0/8] Stop using obsoleted egrep/fgrep
Date: Fri, 24 Jun 2022 14:57:27 +0800 [thread overview]
Message-ID: <74ea0c62ebe19db186263053e4051f81d46e9da4.camel@xry111.site> (raw)
egrep and fgrep have been deprecated for a long time, and the next grep
release will emit a warning if egrep or fgrep is invoked:
https://git.savannah.gnu.org/cgit/grep.git/commit/?id=a951562
To prevent us from a lot of these warnings in the future, we should stop
using egrep and fgrep. These patches will remove most of the use of
egrep or fgrep from GCC building system. The remaining:
* The configure scripts generated by autoconf-2.69 will still refer to
"egrep", but they will try "grep -E" first and only try egrep when
"grep -E" is not available.
* libgo: Left for Ian because I'm not familiar with it.
* maintainer-scripts/update_web_docs_libstdcxx_git: Left for Jonathan
because I don't think other people will invoke it.
* libffi: Already submitted https://github.com/libffi/libffi/pull/720.
* contrib/gen_autofdo_event.py and gcc/config/i386/gcc-auto-profile:
I'll make a patch later (now download.01.org seems down so I can't
test or regenerate gcc-auto-profile) porting gen_autofdo_event.py to
Python 3.
Xi Ruoyao (8):
config: use grep -E instead of egrep
fixincludes: use grep -E/-F instead of egrep/fgrep
libstdc++: use grep -E instead of egrep in scripts
libbacktrace: use grep -F instead of fgrep
intl: stop using fgrep for exgettext
fortran: use grep -F instead of fgrep
testsuite: use grep -E instead of egrep
contrib: use grep -E instead of egrep
config.rpath | 8 ++++----
config/lib-ld.m4 | 4 ++--
configure | 4 ++--
configure.ac | 4 ++--
contrib/check_GNU_style.sh | 10 +++++-----
contrib/test_summary | 2 +-
contrib/warn_summary | 2 +-
fixincludes/fixinc.in | 2 +-
fixincludes/fixincl.x | 10 +++++-----
fixincludes/genfixes | 2 +-
fixincludes/inclhack.def | 6 +++---
gcc/configure | 8 ++++----
gcc/fortran/Make-lang.in | 2 +-
gcc/po/exgettext | 2 +-
gcc/testsuite/ada/acats/run_all.sh | 2 +-
gcc/testsuite/go.test/go-test.exp | 2 +-
intl/configure | 4 ++--
libbacktrace/configure | 2 +-
libbacktrace/configure.ac | 2 +-
libcpp/configure | 4 ++--
libgcc/configure | 2 +-
libstdc++-v3/configure | 4 ++--
libstdc++-v3/scripts/extract_symvers.in | 4 ++--
libstdc++-v3/scripts/run_doxygen | 4 ++--
24 files changed, 48 insertions(+), 48 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-24 6:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 6:57 Xi Ruoyao [this message]
2022-06-24 6:58 ` [PATCH 1/8] config: use grep -E instead of egrep Xi Ruoyao
2022-06-24 7:00 ` [PATCH 2/8] fixincludes: use grep -E/-F instead of egrep/fgrep Xi Ruoyao
2022-06-24 7:02 ` [PATCH 3/8] libstdc++: use grep -E instead of egrep in scripts Xi Ruoyao
2022-06-24 10:00 ` Jonathan Wakely
2022-06-24 11:08 ` Xi Ruoyao
2022-06-24 11:18 ` Jonathan Wakely
2022-06-24 11:35 ` Jonathan Wakely
2022-06-24 11:41 ` Rainer Orth
2022-06-24 12:37 ` Xi Ruoyao
2022-06-24 12:38 ` Jonathan Wakely
2022-06-24 7:04 ` [PATCH 4/8] libbacktrace: use grep -F instead of fgrep Xi Ruoyao
2022-06-24 7:05 ` [PATCH 5/8] intl: stop using fgrep for exgettext Xi Ruoyao
2022-06-24 16:06 ` Joseph Myers
2022-06-25 4:00 ` Xi Ruoyao
2022-06-24 7:06 ` [PATCH 6/8] fortran: use grep -F instead of fgrep Xi Ruoyao
2022-06-24 11:13 ` Bernhard Reutner-Fischer
2022-06-24 12:22 ` Xi Ruoyao
2022-06-24 12:35 ` Rainer Orth
2022-06-24 18:30 ` Bernhard Reutner-Fischer
2022-06-24 13:58 ` Thomas Koenig
2022-06-24 7:09 ` [PATCH 7/8] testsuite: use grep -E instead of egrep Xi Ruoyao
2022-06-24 10:57 ` Arnaud Charlet
2022-06-24 7:10 ` [PATCH 8/8] contrib: " Xi Ruoyao
2022-06-24 7:24 ` [PATCH 0/8] Stop using obsoleted egrep/fgrep Rainer Orth
2022-06-24 7:27 ` Xi Ruoyao
2022-06-24 7:50 ` Rainer Orth
2022-06-24 8:26 ` Fangrui Song
2022-06-24 8:33 ` Andrew Pinski
2022-06-24 16:09 ` Joseph Myers
2022-06-24 16:21 ` Iain Sandoe
2022-06-24 8:45 ` Rainer Orth
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=74ea0c62ebe19db186263053e4051f81d46e9da4.camel@xry111.site \
--to=xry111@xry111.site \
--cc=gcc-patches@gcc.gnu.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).