Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Markus Deuling <deuling@de.ibm.com>
Subject: Re: [patch] Testsuite: Fortran: 6.8 regression + gfortran updates
Date: Wed, 07 Jan 2009 05:14:00 -0000	[thread overview]
Message-ID: <20090107051404.GI3664@adacore.com> (raw)
In-Reply-To: <20090106140516.GA16916@host0.dyn.jankratochvil.net>

> gdb/
> 2009-01-06  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* f-typeprint.c (f_type_print_base <TYPE_CODE_STRUCT>): Fix output
> 	spacing, a regression from 2008-04-22.

I am not sure about this part - the use of the "indented" printf seems
to be pretty deliberate, and we find this use elsewhere for the other
kinds of types. Looks like Fortran developers like indented type names?
I think it'd be interesting to get Markus' opinion.

This, in turn, conditions the changes to the testsuite, but it should
only be minimal.

> gdb/testsuite/
> 2009-01-06  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
>         * gdb.fortran/derived-type.exp: New variables int4 and real4.  Match
>         now the output exactly, using less wildcards.  Expect also the output
>         of gfortran-4.3.  Update for the f-valprint.c modification from
>         2008-04-22.
>         * gdb.fortran/subarray.exp: Expect also the output of gfortran-4.3.
>         Remove gdb_test test names where matching the command.

Overall, the changes look OK to me. The only adjustment that might be
needed is if we keep (f_type_print_base <TYPE_CODE_STRUCT>) as is.

-- 
Joel


  parent reply	other threads:[~2009-01-07  5:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 18:16 Jan Kratochvil
2008-12-29  3:49 ` Joel Brobecker
2009-01-06 14:05   ` Jan Kratochvil
2009-01-06 14:14     ` Jan Kratochvil
2009-01-07  5:14     ` Joel Brobecker [this message]
2009-01-07  7:38       ` Jan Kratochvil
2009-01-07  8:46         ` Joel Brobecker
2009-01-07 12:44           ` Jan Kratochvil

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=20090107051404.GI3664@adacore.com \
    --to=brobecker@adacore.com \
    --cc=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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