From: Nils-Christian Kempke <nils-christian.kempke@intel.com>
To: gdb-patches@sourceware.org
Cc: tom@tromey.com, Nils-Christian Kempke <nils-christian.kempke@intel.com>
Subject: [PATCH v2 0/4] Adapt Fortran testsuite for ifort
Date: Wed, 31 Aug 2022 11:36:46 +0200 [thread overview]
Message-ID: <20220831093650.674582-1-nils-christian.kempke@intel.com> (raw)
Hi!
Please find attached v2 of this series.
V1 can be found here:
https://sourceware.org/pipermail/gdb-patches/2022-June/190013.html
V2 incorporates Tom's comment on patch 3/4 here:
https://sourceware.org/pipermail/gdb-patches/2022-August/191606.html
so changes from v1 to v2 only concern patch 3:
* Patch 1: unchanged.
* Patch 2: unchanged.
* Patch 3: Remove fortran_runto_main for the two tests as well as the
first breakpoint setting + hitting and instead use runto to directly
run to the first breakpoint location.
* Patch 4: unchanged.
Tom has approved of Patch 1, 2, and 4 otherwise, but if anyone has a
comment, they are always welcome!
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 | 13 +++++--------
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 | 11 +++--------
7 files changed, 27 insertions(+), 25 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
next reply other threads:[~2022-08-31 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 9:36 Nils-Christian Kempke [this message]
2022-08-31 9:36 ` [PATCH v2 1/4] testsuite, fortran: make mixed-lang-stack less compiler dependent Nils-Christian Kempke
2022-08-31 9:36 ` [PATCH v2 2/4] testsuite, fortran: Remove self assignment non-statements Nils-Christian Kempke
2022-08-31 9:36 ` [PATCH v2 3/4] testsuite, fortran: adapt tests for ifort's 'start' behavior Nils-Christian Kempke
2022-08-31 9:36 ` [PATCH v2 4/4] testsuite, fortran: make kfail gfortran specific Nils-Christian Kempke
2022-09-19 10:18 ` [PING][PATCH v2 0/4] Adapt Fortran testsuite for ifort Kempke, Nils-Christian
2022-09-19 10:18 ` Kempke, Nils-Christian
2022-09-26 14:02 ` [PING 2][PATCH " Kempke, Nils-Christian
2022-09-26 14:02 ` Kempke, Nils-Christian
2022-10-05 20:23 ` [PING 3][PATCH " Kempke, Nils-Christian
2022-10-05 20:23 ` Kempke, Nils-Christian
2022-10-13 8:52 ` [PING 4][PATCH " Kempke, Nils-Christian
2022-10-13 8:52 ` Kempke, Nils-Christian
2022-10-21 8:15 ` [PING 5][PATCH " Kempke, Nils-Christian
2022-10-21 8:15 ` Kempke, Nils-Christian
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=20220831093650.674582-1-nils-christian.kempke@intel.com \
--to=nils-christian.kempke@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).