From: Doug Evans <dje@google.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Remove apply_val_pretty_printer parameter valaddr
Date: Thu, 10 Nov 2016 17:53:00 -0000 [thread overview]
Message-ID: <CADPb22ROFAsdD58EYJSiWQp3k3oz9UK3emA0bSqpDWbjtQW=8g@mail.gmail.com> (raw)
In-Reply-To: <1478789679-30957-2-git-send-email-yao.qi@linaro.org>
On Thu, Nov 10, 2016 at 6:54 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
> This patch removes the parameter valaddr of
> extension_language_ops::apply_val_pretty_printer and remove const from
> "struct value *val". valaddr can be got in each extension language's
> implementation of apply_val_pretty_printer.
>
> gdb:
>
> 2016-11-10 Yao Qi <yao.qi@linaro.org>
>
> * cp-valprint.c (cp_print_value): Remove local base_valaddr.
> * extension-priv.h (struct extension_language_ops)
> <apply_val_pretty_printer>: Remove the second parameter.
> Remove const from "struct value *". Callers updated.
> * extension.c (apply_ext_lang_val_pretty_printer): Update
> comments. Remove parameter valaddr. Remove const from
> "struct value *".
> * extension.h (apply_ext_lang_val_pretty_printer): Update
> declaration.
> * guile/guile-internal.h (gdbscm_apply_val_pretty_printer):
> Update declaration.
> * guile/scm-pretty-print.c (gdbscm_apply_val_pretty_printer):
> Remove parameter valaddr. Remove const from "struct value *".
> * python/py-prettyprint.c (gdbpy_apply_val_pretty_printer):
> Likewise.
> * python/python-internal.h (gdbpy_apply_val_pretty_printer):
> Update declaration.
LGTM
next prev parent reply other threads:[~2016-11-10 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 14:54 [PATCH 1/2] Remove parameter valaddr from c print functions Yao Qi
2016-11-10 14:54 ` [PATCH 2/2] Remove apply_val_pretty_printer parameter valaddr Yao Qi
2016-11-10 17:53 ` Doug Evans [this message]
2016-11-10 17:54 ` [PATCH 1/2] Remove parameter valaddr from c print functions Doug Evans
2016-11-11 8:41 ` Yao Qi
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='CADPb22ROFAsdD58EYJSiWQp3k3oz9UK3emA0bSqpDWbjtQW=8g@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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