From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] ada-lang.c:coerce_unspec_val_to_type: Preserve laziness.
Date: Fri, 05 Jul 2013 10:41:00 -0000 [thread overview]
Message-ID: <51D6A2CE.7080502@redhat.com> (raw)
In-Reply-To: <51D6A00A.2050803@broadcom.com>
On 07/05/2013 11:29 AM, Andrew Burgess wrote:
> On 04/07/2013 7:22 PM, Pedro Alves wrote:
>> ada-lang.c:coerce_unspec_val_to_type does:
>>
>> if (value_lazy (val)
>> || TYPE_LENGTH (type) > TYPE_LENGTH (value_type (val)))
>> result = allocate_value_lazy (type);
>> else
>> {
>> result = allocate_value (type);
>> memcpy (value_contents_raw (result), value_contents (val),
>> TYPE_LENGTH (type));
>> }
>> set_value_component_location (result, val);
>> set_value_bitsize (result, value_bitsize (val));
>> set_value_bitpos (result, value_bitpos (val));
>> set_value_address (result, value_address (val));
>> set_value_optimized_out (result, value_optimized_out (val));
>>
>> Notice that before value_optimized_out was made to auto-fetch lazy
>> values, VAL would end up still lazy if it was lazy on entry. It's not
>> really a problem here if VAL is lazy, and VAL->optimized_out is 0,
>> because RESULT is also left lazy. IOW, this just wants to copy the
>> VAL->optimized_out flag to RESULT->optimized_out, nothing else.
>>
>> The patch adds the value_optimized_out_const function for that.
>
> As an alternative, this patch avoids the new _const function,
> I move the setting of the optimized_out value into the else case where we know val is no longer lazy.
>
> Cheers,
> Andrew
>
>
> diff --git a/gdb/ada-lang.c b/gdb/ada-lang.c
> index 8240fee..ea7b579 100644
> --- a/gdb/ada-lang.c
> +++ b/gdb/ada-lang.c
> @@ -576,12 +576,14 @@ coerce_unspec_val_to_type (struct value *val, struct type *type)
> result = allocate_value (type);
> memcpy (value_contents_raw (result), value_contents (val),
> TYPE_LENGTH (type));
> + /* Only copy the optimized out setting if val is not lazy. If it
> + is lazy then the optimized_out flag will always be false. */
> + set_value_optimized_out (result, value_optimized_out (val));
> }
> set_value_component_location (result, val);
> set_value_bitsize (result, value_bitsize (val));
> set_value_bitpos (result, value_bitpos (val));
> set_value_address (result, value_address (val));
> - set_value_optimized_out (result, value_optimized_out (val));
> return result;
That works, but I had originally discarded such an approach
because it looked brittle to me. E.g., I was toying with optimizing
value_optimized_out by only fetching lazy values if it really can't
avoid it, and such a change would render this subtly broken.
--
Pedro Alves
next prev parent reply other threads:[~2013-07-05 10:41 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 [this message]
2013-07-10 17:13 ` Tom Tromey
2013-07-26 17:08 ` Pedro Alves
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=51D6A2CE.7080502@redhat.com \
--to=palves@redhat.com \
--cc=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
/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