From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@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: Mon, 17 Jan 2011 16:20:00 -0000 [thread overview]
Message-ID: <m3fwsrldey.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110111170634.GA29563@host1.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue, 11 Jan 2011 18:06:35 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> But in practice I do not think it is a problem as there is already
Jan> a problem if one attempts to copy a huge array into an internal
Jan> variable. And in most cases the value is lazy which is OK.
One way we could try to solve our problems with very large arrays is to
support partially read in values using lval_funcs, sort of like we do
for optimized out pieces. We could just read the bits we actually use
in some way. I think this isn't quite as simple as optimized out
pieces, though, because we'd have to change GDB to recognize that a
value's contents may come in segments.
Tom
prev parent reply other threads:[~2011-01-17 16:10 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
2011-01-12 16:31 ` Jan Kratochvil
2011-01-17 16:20 ` 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=m3fwsrldey.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aburgess@broadcom.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