From: Sami Wagiaalla <swagiaal@redhat.com>
To: archer@sourceware.org
Subject: Re: [rfc] patch for pr8880
Date: Tue, 09 Feb 2010 19:23:00 -0000 [thread overview]
Message-ID: <4B71B645.2050806@redhat.com> (raw)
In-Reply-To: <m33a1b8wkn.fsf@fleche.redhat.com>
On 02/08/2010 12:30 PM, Tom Tromey wrote:
>>>>>> "Sami" == Sami Wagiaalla<swagiaal@redhat.com> writes:
>
> Sami> This was a long chase but an easy fix.
> Sami> Thoughts ?
>
> Lots of formatting nits.
>
> Also I have a few more substantive comments.
>
> Sami> +struct value *
> Sami> +value_at_value (struct value *value)
> Sami> +{
> Sami> + return value_at(TYPE_TARGET_TYPE (value_type(value)),
> Sami> + value_as_address(value));
>
> Why not just use value_ind?
>
value_ind works. I just missed it :)
> Sami> @@ -2104,6 +2111,9 @@ value_struct_elt (struct value **argp, struct value **args,
>
> Modifying value_struct_elt seems dangerous. This is called from many
> places in the code, including some which don't expect ADL to be used --
> e.g., Java, Ada.
>
> Can this be done by the caller somehow instead?
> Or perhaps some refactoring is needed.
>
I could put this code in a function to be called from value_x_binop and
value_x_unop. That would at least avoid the awkward argument counting
but not earlier than that since the arguments need to have been
evaluated and/or add a check for la_language == language_cplus.
> Also, ADL should only be done for unqualified names.
> It isn't clear to me that this change satisfies that requirement.
>
Let me look into this. It might be a general problem I don't think gdb
ever differentiates between qualified and unqualified names
next prev parent reply other threads:[~2010-02-09 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 16:35 Sami Wagiaalla
2010-02-08 17:30 ` Tom Tromey
2010-02-09 19:23 ` Sami Wagiaalla [this message]
2010-02-09 23:35 ` Tom Tromey
2010-02-11 21:00 ` Tom Tromey
2010-02-12 15:44 ` Sami Wagiaalla
2010-02-18 19:45 ` Sami Wagiaalla
2010-02-19 23:23 ` Tom Tromey
2010-02-22 16:37 ` Sami Wagiaalla
2010-02-23 22:32 ` 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=4B71B645.2050806@redhat.com \
--to=swagiaal@redhat.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).