Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Andrew Burgess <aburgess@broadcom.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] ada-lang.c:coerce_unspec_val_to_type: Preserve laziness.
Date: Fri, 26 Jul 2013 17:08:00 -0000	[thread overview]
Message-ID: <51F2ACF3.1000902@redhat.com> (raw)
In-Reply-To: <87mwpugwxy.fsf@fleche.redhat.com>

On 07/10/2013 06:13 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
> 
> Pedro> That works, but I had originally discarded such an approach
> Pedro> because it looked brittle to me.  E.g., I was toying with optimizing
> Pedro> value_optimized_out by only fetching lazy values if it really can't
> Pedro> avoid it, and such a change would render this subtly broken.
> 
> This code in ada-lang.c and similar code elsewhere always seems to me to
> be a call for a new value copy-constructor that takes a type argument.
> Then any necessary wackiness can be isolated in value.c.

Yeah!  The deprecated_set_value_type calls have tended to morph into things
like that.  I had actually started out with something like that, noticing
that this Ada code is like a reinterpret cast.  I did something based on
refactoring value_copy, but wasn't getting happy with the results (or rather,
the time it was taking me), so I gave up.   But I'd definitely support
it if someone went along those lines.

-- 
Pedro Alves


  reply	other threads:[~2013-07-26 17:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 18:23 Pedro Alves
2013-07-05 10:29 ` Andrew Burgess
2013-07-05 10:41   ` Pedro Alves
2013-07-10 17:13     ` Tom Tromey
2013-07-26 17:08       ` Pedro Alves [this message]
2013-07-10  0:44 ` Joel Brobecker
2013-07-26 17:15   ` Pedro Alves

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=51F2ACF3.1000902@redhat.com \
    --to=palves@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