Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siva Chandra <sivachandra@google.com>
To: gdb-patches <gdb-patches@sourceware.org>,
	Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [PATCH v4] Make chained function calls in expressions work
Date: Mon, 03 Nov 2014 14:35:00 -0000	[thread overview]
Message-ID: <CAGyQ6gzc+32oXZ7MNedV4_hN6_isQZCGO3iD=ZCi5bTgvgaMog@mail.gmail.com> (raw)
In-Reply-To: <CAGyQ6gxhqVQW6eF-ay1UfcW2WgPoa=6=0DJ70dDeWEMJq9By2A@mail.gmail.com>

On Sat, Oct 25, 2014 at 7:24 AM, Siva Chandra <sivachandra@google.com> wrote:
> This is a follow up to the thread here:
> https://sourceware.org/ml/gdb-patches/2014-10/msg00000.html
>
> I have made all the suggested changes which now eliminates the need
> for two patches in this set. The single patch is attached.
>
> gdb/ChangeLog:
>
> 2014-10-25  Siva Chandra Reddy  <sivachandra@google.com>
>
>         * eval.c (evaluate_expression): Cleanup stack mirrors that might
>         have been created.
>         (add_value_to_expression_stack, skip_current_expression_stack):
>         New functions.
>         * expression.h (struct expression): New field
>         'on_stack_temporaries_vec'.
>         * gdbtypes.c (class_or_union_p): New function.
>         * gdbtypes.h (class_or_union_p): Declare.
>         * infcall.c (call_function_by_hand): New argument EXP of type
>         struct expression *. Setup stack temporaries for return values of
>         class type.
>         (get_return_value_from_memory): New function.
>         * infcall.h (call_function_by_hand): Update signature and all
>         callers.
>         * valarith.c (value_x_binop): New argument EXP of type
>         struct expression *.
>         (value_x_unop): Likewise.
>         * value.c (write_value_to_memory): New function.
>         (value_fetch_lazy): Fix its description comment.
>         * value.h (add_value_to_expression_stack)
>         (skip_current_expression_stack, write_value_to_memory): Declare.
>         (value_x_binop, value_x_unop): Update signature and all callers.
>
> gdb/testsuite/ChangeLog:
>
> 2014-10-25  Siva Chandra Reddy  <sivachandra@google.com>
>
>         * gdb.cp/chained-calls.cc: New file.
>         * gdb.cp/chained-calls.exp: New file.
>         * gdb.cp/smartp.exp: Remove KFAIL from c2->inta.

Ping.


  reply	other threads:[~2014-11-03 14:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 14:24 Siva Chandra
2014-11-03 14:35 ` Siva Chandra [this message]
2014-11-03 14:43 ` Ulrich Weigand
2014-11-03 19:55   ` Siva Chandra
2014-11-03 21:22     ` Siva Chandra
2014-11-04 13:43       ` Ulrich Weigand
2014-11-04 15:08         ` Siva Chandra
2014-11-04 15:40           ` Ulrich Weigand
2014-11-04 13:38     ` Ulrich Weigand
2014-11-04 14:26       ` Siva Chandra
2014-11-04 14:59         ` Ulrich Weigand
2014-11-04 15:23           ` Siva Chandra
2014-11-04 15:40             ` Ulrich Weigand
2014-11-11 14:55               ` Siva Chandra
2014-11-11 15:00                 ` Siva Chandra
2014-11-11 15:21                   ` Ulrich Weigand
2014-11-11 17:05                     ` Siva Chandra
2014-11-12 16:08                     ` Doug Evans
2014-11-12 17:29                       ` Doug Evans
2014-11-13  3:00                       ` Siva Chandra

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='CAGyQ6gzc+32oXZ7MNedV4_hN6_isQZCGO3iD=ZCi5bTgvgaMog@mail.gmail.com' \
    --to=sivachandra@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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