From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Andrew Burgess <aburgess@broadcom.com>
Subject: Re: [patch 2/2] Multi-dimensional arrays issue (PR fortran/11104)
Date: Tue, 11 Jan 2011 17:26:00 -0000 [thread overview]
Message-ID: <20110111170634.GA29563@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <m38vyrjsf8.fsf@fleche.redhat.com>
On Tue, 11 Jan 2011 17:50:35 +0100, Tom Tromey wrote:
> I read this and at least the parts that I understood make sense to me :)
> I think you should go ahead with it.
I was thinking that even with the patch 1/2 there is a memory requirements
regression:
If you have a value containing the array (such as $var) it is not lazy. The
new code will create the memory copies of the intermediate array subsections.
The current FSF GDB code did not.
But in practice I do not think it is a problem as there is already a problem
if one attempts to copy a huge array into an internal variable. And in most
cases the value is lazy which is OK.
Thanks,
Jan
next prev parent reply other threads:[~2011-01-11 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 12:03 Jan Kratochvil
2011-01-11 16:50 ` Tom Tromey
2011-01-11 17:26 ` Jan Kratochvil [this message]
2011-01-12 16:31 ` Jan Kratochvil
2011-01-17 16:20 ` 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=20110111170634.GA29563@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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