From: Tom Tromey <tom@tromey.com>
To: Nils-Christian Kempke via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 3/4] testsuite, fortran: adapt tests for ifort's 'start' behavior
Date: Tue, 30 Aug 2022 13:51:37 -0600 [thread overview]
Message-ID: <87czcha4s6.fsf@tromey.com> (raw)
In-Reply-To: <20220610154500.374897-4-nils-christian.kempke@intel.com> (Nils-Christian Kempke via Gdb-patches's message of "Fri, 10 Jun 2022 17:44:59 +0200")
>>>>> Nils-Christian Kempke via Gdb-patches <gdb-patches@sourceware.org> writes:
> -gdb_continue_to_breakpoint "First Breakpoint"
> +# Ifort is already at this line after runto_main.
> +if { ![test_compiler_info {ifort-*} f90] } {
> + gdb_continue_to_breakpoint "First Breakpoint"
> +}
I suspect that in this particular test it would be more robust to simply
run to this first breakpoint and not try to run to main. That way the
test would be independent of where the compiler chooses to emit the
'main' entry point.
Tom
next prev parent reply other threads:[~2022-08-30 19:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:44 [PATCH 0/4] Adapt Fortran testsuite for ifort 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 [this message]
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 ` [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=87czcha4s6.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).