From: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
Subject: Re: [PING 6][PATCH 0/4] Adapt Fortran testsuite for ifort
Date: Tue, 30 Aug 2022 14:47:00 +0000 [thread overview]
Message-ID: <CY4PR1101MB20716E6E040CB95D64FE6C43B8799@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
Message-ID: <20220830144700.Uk_2lfr8ZoTWi-Z3Ju4nGL9rjZi15cJ0fVDSTXe4MDE@z> (raw)
In-Reply-To: <CY4PR1101MB2071147BB493BD532E1D012DB8709@CY4PR1101MB2071.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 5735 bytes --]
Ping!
Thanks,
Nils
________________________________
From: Gdb-patches <gdb-patches-bounces+nils-christian.kempke=intel.com@sourceware.org> on behalf of Kempke, Nils-Christian via Gdb-patches <gdb-patches@sourceware.org>
Sent: Tuesday, August 23, 2022 4:43 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Subject: Re: [PING 5][PATCH 0/4] Adapt Fortran testsuite for ifort
Ping!,
Thanks,
Nils
________________________________
From: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Sent: Monday, August 8, 2022 2:53 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>; Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Subject: Re: [PING 4][PATCH 0/4] Adapt Fortran testsuite for ifort
Ping!,
Thanks,
Nils
________________________________
From: Gdb-patches <gdb-patches-bounces+nils-christian.kempke=intel.com@sourceware.org> on behalf of Kempke, Nils-Christian via Gdb-patches <gdb-patches@sourceware.org>
Sent: Wednesday, July 27, 2022 7:14 AM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Subject: Re: [PING 4][PATCH 0/4] Adapt Fortran testsuite for ifort
Ping!,
Thanks,
Nils
________________________________
From: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Sent: Tuesday, July 12, 2022 2:55 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>; Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Subject: [PING 3][PATCH 0/4] Adapt Fortran testsuite for ifort
Ping!
Thanks,
Nils
________________________________
From: Gdb-patches <gdb-patches-bounces+nils-christian.kempke=intel.com@sourceware.org> on behalf of Kempke, Nils-Christian via Gdb-patches <gdb-patches@sourceware.org>
Sent: Monday, July 4, 2022 5:59 PM
To: gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Subject: [PING 2][PATCH 0/4] Adapt Fortran testsuite for ifort
Ping!
Cheers,
Nils
________________________________
From: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
Sent: Friday, June 10, 2022 5:44 PM
To: gdb-patches@sourceware.org <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> <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
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de<http://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
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de<http://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
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 prev parent reply other threads:[~2022-08-30 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:44 [PATCH " Nils-Christian Kempke
2022-06-10 15:44 ` [PATCH 1/4] testsuite, fortran: make mixed-lang-stack less compiler dependent Nils-Christian Kempke
2022-06-10 15:44 ` [PATCH 2/4] testsuite, fortran: Remove self assignment non-statements Nils-Christian Kempke
2022-06-10 15:44 ` [PATCH 3/4] testsuite, fortran: adapt tests for ifort's 'start' behavior Nils-Christian Kempke
2022-08-30 19:51 ` Tom Tromey
2022-08-31 9:32 ` Kempke, Nils-Christian
2022-08-31 17:22 ` Tom Tromey
2022-06-10 15:45 ` [PATCH 4/4] testsuite, fortran: make kfail gfortran specific Nils-Christian Kempke
2022-07-04 15:59 ` [PING 2][PATCH 0/4] Adapt Fortran testsuite for ifort Kempke, Nils-Christian
2022-07-12 12:55 ` [PING 3][PATCH " Kempke, Nils-Christian
2022-07-27 5:14 ` [PING 4][PATCH " Kempke, Nils-Christian
2022-08-08 12:53 ` Kempke, Nils-Christian
2022-08-23 14:43 ` [PING 5][PATCH " Kempke, Nils-Christian
2022-08-30 14:47 ` Kempke, Nils-Christian [this message]
2022-08-30 14:47 ` [PING 6][PATCH " Kempke, Nils-Christian
2022-08-30 19:52 ` [PATCH " Tom Tromey
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=CY4PR1101MB20716E6E040CB95D64FE6C43B8799@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).