From: Siva Chandra <sivachandra@google.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v6] Make chained function calls in expressions work
Date: Sat, 29 Nov 2014 00:04:00 -0000 [thread overview]
Message-ID: <CAGyQ6gxFV2tgp64u9+2jsf82FUeenqNDaJQnS2C3zK0xTSBKFQ@mail.gmail.com> (raw)
In-Reply-To: <201411281210.sASCAQGP013169@d03av02.boulder.ibm.com>
On Fri, Nov 28, 2014 at 4:10 AM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
> Siva Chandra wrote:
>
>> gdb/ChangeLog:
>>
>> 2014-11-27 Siva Chandra Reddy <sivachandra@google.com>
>>
>> * eval.c: Include gdbthread.h.
>> (evaluate_subexp): Enable thread stack temporaries before
>> evaluating a complete expression and clean them up after the
>> evaluation is complete.
>> * gdbthread.h: Include common/vec.h.
>> (value_ptr): New typedef.
>> (VEC (value_ptr)): New vector type.
>> (value_vec): New typedef.
>> (struct thread_info): Add new fields stack_temporaries_enabled
>> and stack_temporaries.
>> (enable_thread_stack_temporaries)
>> (thread_stack_temporaries_enabled_p, push_thread_stack_temporary)
>> (get_last_thread_stack_temporary)
>> (value_in_thread_stack_temporaries): Declare.
>> * gdbtypes.c (class_or_union_p): New function.
>> * gdbtypes.h (class_or_union_p): Declare.
>> * infcall.c (call_function_by_hand): Store return values of class
>> type as temporaries on stack.
>> * thread.c (enable_thread_stack_temporaries): New function.
>> (thread_stack_temporaries_enabled_p, push_thread_stack_temporary)
>> (get_last_thread_stack_temporary): Likewise.
>> (value_in_thread_stack_temporaries): Likewise.
>> * value.c (value_force_lval): New function.
>> * value.h (value_force_lval): Declare.
>>
>> gdb/testsuite/ChangeLog:
>>
>> 2014-11-27 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 for "p c2->inta".
>
> This is OK.
>
> Thanks for you patience in working through the many iterations on this patch!
Thanks for your patience with explaining things to me. I have now
pushed this patch after fixing the one comment:
6c659fc2c7cd2da6d2b9a3d7c38597ad3821832a
next prev parent reply other threads:[~2014-11-29 0:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 6:55 Siva Chandra
2014-11-28 12:10 ` Ulrich Weigand
2014-11-29 0:04 ` Siva Chandra [this message]
2014-11-29 8:26 ` Regression for gdb.cp/exceptprint.exp [Re: [PATCH v6] Make chained function calls in expressions work] Jan Kratochvil
2014-11-29 8:59 ` Siva Chandra
2014-11-29 9:13 ` Jan Kratochvil
2014-11-29 10:16 ` Siva Chandra
2014-11-29 12:38 ` Jan Kratochvil
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=CAGyQ6gxFV2tgp64u9+2jsf82FUeenqNDaJQnS2C3zK0xTSBKFQ@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).