public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [PING] [PATCH 0/4] Adapt Fortran testsuite for ifort
Date: Mon, 27 Jun 2022 04:59:29 +0000	[thread overview]
Message-ID: <CY4PR1101MB2071891BECCD6584DA4F810FB8B99@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)

Ping!

Thanks, Nils

> -----Original Message-----
> From: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
> Sent: Friday, June 10, 2022 5:45 PM
> To: gdb-patches@sourceware.org
> Cc: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
> Subject: [PATCH 0/4] Adapt Fortran testsuite for ifort
> 
> Hi,
> 
> there were a few places in the testsuite where ifort's behavior was
> FAILing the tests and where I think this is not the result of an ifort
> bug but rather of a testsuite not forgiving enough.
> 
> The attached patches should not change the behavior for any other
> compiler, and I could not find any regressions with gfortran/ifx (tested
> with unix, unix/m32, native-gdbserver and native-extended-gdbserver).
> 
> For ifort this series improves testsuite performance if compared to the
> current master:
> 
> master before series:
> 
>                 === gdb Summary ===
> 
>   # of expected passes            5771
>   # of unexpected failures        238
>   # of unknown successes          1
>   # of known failures             1
>   # of untested testcases         1
>   # of unresolved testcases       3
>   # of unsupported tests          5
>   # of duplicate test names       3
> 
> master after series:
> 
>                 === gdb Summary ===
> 
>   # of expected passes            5847
>   # of unexpected failures        161
>   # of known failures             1
>   # of untested testcases         1
>   # of unresolved testcases       3
>   # of unsupported tests          5
>   # of duplicate test names       3
> 
> 
> Any feedback is appreciated,
> 
> Cheers,
> Nils
> 
> Nils-Christian Kempke (4):
>   testsuite, fortran: make mixed-lang-stack less compiler dependent
>   testsuite, fortran: Remove self assignment non-statements
>   testsuite, fortran: adapt tests for ifort's 'start' behavior
>   testsuite, fortran: make kfail gfortran specific
> 
>  gdb/testsuite/gdb.fortran/array-slices-bad.exp    |  5 ++++-
>  gdb/testsuite/gdb.fortran/function-calls.exp      |  4 +++-
>  gdb/testsuite/gdb.fortran/library-module-lib.f90  |  2 +-
>  gdb/testsuite/gdb.fortran/library-module-main.f90 |  2 +-
>  gdb/testsuite/gdb.fortran/mixed-lang-stack.exp    |  9 ++++++++-
>  gdb/testsuite/gdb.fortran/module.f90              | 11 ++++++-----
>  gdb/testsuite/gdb.fortran/vla-type.exp            |  5 +++--
>  7 files changed, 26 insertions(+), 12 deletions(-)
> 
> --
> 2.25.1

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


                 reply	other threads:[~2022-06-27  4:59 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=CY4PR1101MB2071891BECCD6584DA4F810FB8B99@CY4PR1101MB2071.namprd11.prod.outlook.com \
    --to=nils-christian.kempke@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).