RE: [PATCH 3/4] testsuite, fortran: adapt tests for ifort's 'start' behavior

["Kempke, Nils-Christian" <nils-christian.kempke@intel.com>]

Hi Tom,

Yes, that is true.. But I think that would also hold true for the 
gdb.fortran/vla-type.exp test then - where both, ifort and flang
skip all variable declaration statements, too.  Or do you see a
difference there?

I'll change this patch for both tests and remove the
get_compiler_info checks as well as the fortran_run_to_main call
for now.  Instead I'll directly call the 'runto'.

Thanks!

Nils

> -----Original Message-----
> From: Tom Tromey <tom@tromey.com>
> Sent: Tuesday, August 30, 2022 9:52 PM
> To: Nils-Christian Kempke via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Kempke, Nils-Christian <nils-christian.kempke@intel.com>
> Subject: Re: [PATCH 3/4] testsuite, fortran: adapt tests for ifort's 'start'
> behavior
> 
> >>>>> 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
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