From: Siva Chandra <sivachandra@google.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Enable invoking overloaded operator() method on class and union values.
Date: Thu, 20 Nov 2014 17:02:00 -0000 [thread overview]
Message-ID: <CAGyQ6gw1EahNpMhcDqi9sUFN4ChH1fa5Tadbnxgmh+nFFK5i0g@mail.gmail.com> (raw)
In-Reply-To: <CAGyQ6gxeuscNqvqgrt=Secw5C+dqyLyXebm_GuNgpjZZYddRgQ@mail.gmail.com>
On Thu, Nov 20, 2014 at 8:56 AM, Siva Chandra <sivachandra@google.com> wrote:
> Hello,
>
> The attached patch enables invoking overloaded operator() method on
> class and union values when evaluating expressions.
>
> [I expected that once this feature is in, invoking c++ lambdas would
> also be possible naturally. However, It does not happen and I am
> working on that.]
To clarify, I do not think it is because of a deficiency in my patch,
but because the debug info for lambdas is not read in and handled
appropriately in GDB.
> gdb/ChangeLog:
>
> 2014-11-20 Siva Chandra Reddy <sivachandra@google.com>
>
> * eval.c (evaluate_subexp_standard): Extend handling of
> OP_FUNCALL operation to enable invoking overloaded
> operator() methods.
> * gdbtypes.c (class_or_union_p): New function.
> * gdbtypes.h (class_or_union_p): Declare.
>
> gdb/testsuite/ChangeLog:
>
> 2014-11-20 Siva Chandra Reddy <sivachandra@google.com>
>
> * gdb.cp/member-ptr.exp: Modify expected pattern of
> "print diamond.*diamond_pfunc_ptr (20)" and
> "print diamond.*left_vpmf ()".
> * gdb.cp/paren-op.cc: New file.
> * gdb.cp/paren-op.exp: New file.
>
> Regression tested on x86_64 GNU/Linux.
>
> Thank you,
> Siva Chandra
next prev parent reply other threads:[~2014-11-20 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 16:56 Siva Chandra
2014-11-20 17:02 ` Siva Chandra [this message]
2014-12-01 8:32 ` Siva Chandra
2015-01-07 6:26 ` 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=CAGyQ6gw1EahNpMhcDqi9sUFN4ChH1fa5Tadbnxgmh+nFFK5i0g@mail.gmail.com \
--to=sivachandra@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).