From: Felix Willgerodt <felix.willgerodt@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/2] Testsuite changes for clang and icc/icx.
Date: Mon, 25 Jul 2022 13:38:20 +0200 [thread overview]
Message-ID: <20220725113822.1855437-1-felix.willgerodt@intel.com> (raw)
V1 was only one patch and can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-June/189903.html
When discussing this patch, we discovered that the float/double change in
callfuncs.c was actually not really necessary. Hence I removed it in V2.
V2 also adds a new patch to add "-Wno-unknown-warning-option" for icc and icx
compilation in the testsuite, similar to how it is already done for clang.
This enables more tests to run with icc and icx.
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 | 2 +-
gdb/testsuite/lib/gdb.exp | 10 +++++++---
2 files changed, 8 insertions(+), 4 deletions(-)
--
2.34.3
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2022-07-25 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 11:38 Felix Willgerodt [this message]
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
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=20220725113822.1855437-1-felix.willgerodt@intel.com \
--to=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).