From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/2] gdb, testsuite: Enable testcases that suppress specific warnings, for icc/icx.
Date: Tue, 26 Jul 2022 18:07:44 -0700 [thread overview]
Message-ID: <20220726180744.42186488@f35-zws-1> (raw)
In-Reply-To: <20220725113822.1855437-2-felix.willgerodt@intel.com>
On Mon, 25 Jul 2022 13:38:21 +0200
Felix Willgerodt via Gdb-patches <gdb-patches@sourceware.org> wrote:
> To cite gdb.exp:
> Some C/C++ testcases unconditionally pass -Wno-foo as additional
> options to disable some warning. That is OK with GCC, because
> by design, GCC accepts any -Wno-foo option, even if it doesn't
> support -Wfoo. Clang however warns about unknown -Wno-foo by
> default, unless you pass -Wno-unknown-warning-option as well.
> We do that here, so that individual testcases don't have to
> worry about it.
>
> This patch adds the same option that already exists for clang for icx and
> adds the equivalent icc option.
Okay.
Kevin
next prev parent reply other threads:[~2022-07-27 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 11:38 [PATCH v2 0/2] Testsuite changes for clang and icc/icx Felix Willgerodt
2022-07-25 11:38 ` [PATCH v2 1/2] gdb, testsuite: Enable testcases that suppress specific warnings, for icc/icx Felix Willgerodt
2022-07-27 1:07 ` Kevin Buettner [this message]
2022-07-25 11:38 ` [PATCH v2 2/2] gdb, testsuite: Adapt gdb.base/callfuncs.exp for new clang warning Felix Willgerodt
2022-07-27 1:12 ` Kevin Buettner
2022-07-25 11:45 ` [PATCH v2 0/2] Testsuite changes for clang and icc/icx Willgerodt, Felix
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=20220726180744.42186488@f35-zws-1 \
--to=kevinb@redhat.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).