public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2731] contrib: skip new egrep warning Date: Tue, 20 Sep 2022 08:17:47 +0000 (GMT) [thread overview] Message-ID: <20220920081747.DCE1A3858422@sourceware.org> (raw) https://gcc.gnu.org/g:63e3cc294d835b43701eeef9410d1b8fc8922869 commit r13-2731-g63e3cc294d835b43701eeef9410d1b8fc8922869 Author: Martin Liska <mliska@suse.cz> Date: Tue Sep 20 10:16:47 2022 +0200 contrib: skip new egrep warning contrib/ChangeLog: * filter-clang-warnings.py: Skip egrep: warning: egrep is obsolescent; using grep -E. Diff: --- contrib/filter-clang-warnings.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/contrib/filter-clang-warnings.py b/contrib/filter-clang-warnings.py index 942cd30b659..3c68be028a8 100755 --- a/contrib/filter-clang-warnings.py +++ b/contrib/filter-clang-warnings.py @@ -39,7 +39,7 @@ def skip_warning(filename, message): '-Wignored-attributes', '-Wgnu-zero-variadic-macro-arguments', '-Wformat-security', '-Wundefined-internal', '-Wunknown-warning-option', '-Wc++20-extensions', - '-Wbitwise-instead-of-logical'], + '-Wbitwise-instead-of-logical', 'egrep is obsolescent'], 'insn-modes.cc': ['-Wshift-count-overflow'], 'insn-emit.cc': ['-Wtautological-compare'], 'insn-attrtab.cc': ['-Wparentheses-equality'], @@ -57,8 +57,8 @@ def skip_warning(filename, message): 'lex.cc': ['-Wc++20-attribute-extensions'], } - for name, ignores in ignores.items(): - for i in ignores: + for name, ignore in ignores.items(): + for i in ignore: if name in filename and i in message: return True return False
reply other threads:[~2022-09-20 8:17 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220920081747.DCE1A3858422@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).