From: Tom Tromey <tom@tromey.com>
To: Nils-Christian Kempke via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/4] Adapt Fortran testsuite for ifort
Date: Tue, 30 Aug 2022 13:52:02 -0600 [thread overview]
Message-ID: <878rn5a4rh.fsf@tromey.com> (raw)
In-Reply-To: <20220610154500.374897-1-nils-christian.kempke@intel.com> (Nils-Christian Kempke via Gdb-patches's message of "Fri, 10 Jun 2022 17:44:56 +0200")
>>>>> Nils-Christian Kempke via Gdb-patches <gdb-patches@sourceware.org> writes:
> 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).
I had a comment on patch 3, but otherwise these look fine to me.
Thanks for doing this.
Tom
prev parent reply other threads:[~2022-08-30 19:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:44 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 ` [PING 6][PATCH " Kempke, Nils-Christian
2022-08-30 14:47 ` Kempke, Nils-Christian
2022-08-30 19:52 ` Tom Tromey [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=878rn5a4rh.fsf@tromey.com \
--to=tom@tromey.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).