Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Willgerodt, Felix via Gdb-patches" <gdb-patches@sourceware.org>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: RE: [PATCH v2 0/2] Testsuite changes for clang and icc/icx.
Date: Mon, 25 Jul 2022 11:45:05 +0000	[thread overview]
Message-ID: <MN2PR11MB456654D7DBB0CBBC0F4312778E959@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220725113822.1855437-1-felix.willgerodt@intel.com>

Sorry, I forgot to CC you when sending out my follow-up series.

Felix

> -----Original Message-----
> From: Willgerodt, Felix <felix.willgerodt@intel.com>
> Sent: Montag, 25. Juli 2022 13:38
> To: gdb-patches@sourceware.org
> Cc: Willgerodt, Felix <felix.willgerodt@intel.com>
> Subject: [PATCH v2 0/2] Testsuite changes for clang and icc/icx.
> 
> 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

      parent reply	other threads:[~2022-07-25 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 11:38 Felix Willgerodt via Gdb-patches
2022-07-25 11:38 ` [PATCH v2 1/2] gdb, testsuite: Enable testcases that suppress specific warnings, for icc/icx Felix Willgerodt via Gdb-patches
2022-07-27  1:07   ` Kevin Buettner via Gdb-patches
2022-07-25 11:38 ` [PATCH v2 2/2] gdb, testsuite: Adapt gdb.base/callfuncs.exp for new clang warning Felix Willgerodt via Gdb-patches
2022-07-27  1:12   ` Kevin Buettner via Gdb-patches
2022-07-25 11:45 ` Willgerodt, Felix via Gdb-patches [this message]

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=MN2PR11MB456654D7DBB0CBBC0F4312778E959@MN2PR11MB4566.namprd11.prod.outlook.com \
    --to=gdb-patches@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=felix.willgerodt@intel.com \
    /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