From: Kevin Buettner <kevinb@redhat.com>
To: Felix Willgerodt <felix.willgerodt@intel.com>
Cc: gdb-patches@sourceware.org, aburgess@redhat.com, blarsen@redhat.com
Subject: Re: [PATCH v3 0/2] Testsuite changes for clang and icc/icx
Date: Wed, 27 Jul 2022 10:39:14 -0700 [thread overview]
Message-ID: <20220727103914.055dc0d2@f35-zws-1> (raw)
In-Reply-To: <20220727085128.2404513-1-felix.willgerodt@intel.com>
On Wed, 27 Jul 2022 10:51:26 +0200
Felix Willgerodt <felix.willgerodt@intel.com> wrote:
> V1 was only one patch and can be found here:
> https://sourceware.org/pipermail/gdb-patches/2022-June/189903.html
> V2 can be found here:
> https://sourceware.org/pipermail/gdb-patches/2022-July/191055.html
>
> This series disables some compiler warnings for clang and icc/icx
> in the testsuite.
>
> Since V2 I only added a comment to callfuncs.exp, as requested
> by Kevin Buettner.
>
> Thanks,
> Felix
>
> Felix Willgerodt (2):
> gdb, testsuite: Enable testcases that suppress specific warnings, for
> icc/icx.
> gdb, testsuite: Adapt gdb.base/callfuncs.exp for new clang warning.
>
> gdb/testsuite/gdb.base/callfuncs.exp | 4 +++-
> gdb/testsuite/lib/gdb.exp | 10 +++++++---
> 2 files changed, 10 insertions(+), 4 deletions(-)
This series looks okay to me.
Kevin
next prev parent reply other threads:[~2022-07-27 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 8:51 Felix Willgerodt
2022-07-27 8:51 ` [PATCH v3 1/2] gdb, testsuite: Enable testcases that suppress specific warnings, for icc/icx Felix Willgerodt
2022-07-27 8:51 ` [PATCH v3 2/2] gdb, testsuite: Adapt gdb.base/callfuncs.exp for new clang warning Felix Willgerodt
2022-07-27 17:39 ` Kevin Buettner [this message]
2022-08-10 9:10 ` [PATCH v3 0/2] Testsuite changes for clang and icc/icx Willgerodt, Felix
2022-08-18 7:54 ` Willgerodt, Felix
2022-08-18 16:34 ` Kevin Buettner
2022-08-19 13:08 ` 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=20220727103914.055dc0d2@f35-zws-1 \
--to=kevinb@redhat.com \
--cc=aburgess@redhat.com \
--cc=blarsen@redhat.com \
--cc=felix.willgerodt@intel.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).