Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] Printing of Fortran arrays with dynamic elements
Date: Fri, 26 Jun 2026 10:32:51 -0600	[thread overview]
Message-ID: <87o6gxuurw.fsf@tromey.com> (raw)
In-Reply-To: <33826fc0-b2ab-444e-8fc3-d293f4f7a9e7@suse.de> (Tom de Vries's message of "Sat, 20 Jun 2026 14:38:01 +0200")

>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:

Tom> On 6/19/26 11:42 PM, Tom Tromey wrote:
>> This bug points out a case where a Fortran array has dynamic elements,
>> and each element must have its dynamic type resolved separately.
>> I took the test case directly from the bug, figuring it was ok as
>> the
>> author is at AMD and has some tags in the repository already.
>> 

Tom> LGTM.

Tom> Reviewed-By: Tom de Vries <tdevries@suse.de>

I'm checking this in.

Tom

      reply	other threads:[~2026-06-26 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-19 21:42 Tom Tromey
2026-06-20 12:38 ` Tom de Vries
2026-06-26 16:32   ` 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=87o6gxuurw.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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