public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Convert ada_val_print_ref to value-based API Date: Sat, 14 Mar 2020 00:08:40 +0000 (GMT) [thread overview] Message-ID: <20200314000840.76ED1394B02F@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2e088f8b6ea61fa9db1b592cbd4a6aa80b4e0ab5 commit 2e088f8b6ea61fa9db1b592cbd4a6aa80b4e0ab5 Author: Tom Tromey <tom@tromey.com> Date: Fri Mar 13 17:39:52 2020 -0600 Convert ada_val_print_ref to value-based API This converts ada_val_print_ref to the value-based API by using common_val_print rather than val_print. gdb/ChangeLog 2020-03-13 Tom Tromey <tom@tromey.com> * ada-valprint.c (ada_val_print_ref): Use common_val_print. Diff: --- gdb/ChangeLog | 4 ++++ gdb/ada-valprint.c | 6 ++---- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index b235b0f6d64..78ffe614c95 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2020-03-13 Tom Tromey <tom@tromey.com> + + * ada-valprint.c (ada_val_print_ref): Use common_val_print. + 2020-03-13 Tom Tromey <tom@tromey.com> * ada-valprint.c (ada_value_print_num): New function. diff --git a/gdb/ada-valprint.c b/gdb/ada-valprint.c index 4b89473fef3..1d3b06ddfdd 100644 --- a/gdb/ada-valprint.c +++ b/gdb/ada-valprint.c @@ -1207,10 +1207,8 @@ ada_val_print_ref (struct type *type, const gdb_byte *valaddr, if (value_lazy (deref_val)) value_fetch_lazy (deref_val); - val_print (value_type (deref_val), - value_embedded_offset (deref_val), - value_address (deref_val), stream, recurse + 1, - deref_val, options, language_def (language_ada)); + common_val_print (deref_val, stream, recurse + 1, + options, language_def (language_ada)); } /* See the comment on ada_val_print. This function differs in that it
reply other threads:[~2020-03-14 0:08 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200314000840.76ED1394B02F@sourceware.org \ --to=tromey@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).