Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 1/5] Use ui_out_emit_tuple
Date: Tue, 18 Apr 2017 18:42:00 -0000	[thread overview]
Message-ID: <de26fc98-f0b1-f1e2-575e-733662cbce2e@redhat.com> (raw)
In-Reply-To: <20170414022337.28368-2-tom@tromey.com>

On 04/14/2017 03:23 AM, Tom Tromey wrote:
> This patch changes various places to use ui_out_emit_tuple,
> eliminating a number of cleanups.  This patch only tackles "easy"
> cases, which are ones where the cleanups in question were
> block-structured and did not involve any changes other than the
> obvious replacement.
> 
> 2017-04-13  Tom Tromey  <tom@tromey.com>
> 
> 	* record-btrace.c (record_btrace_insn_history)
> 	(record_btrace_insn_history_range, record_btrace_call_history)
> 	(record_btrace_call_history_range): Use ui_out_emit_tuple.
> 	* thread.c (do_captured_list_thread_ids, print_thread_info_1): Use
> 	ui_out_emit_tuple.
> 	* stack.c (print_frame_info): Use ui_out_emit_tuple.
> 	* solib.c (info_sharedlibrary_command): Use ui_out_emit_tuple.
> 	* skip.c (skip_info): Use ui_out_emit_tuple.
> 	* remote.c (show_remote_cmd): Use ui_out_emit_tuple.
> 	* progspace.c (print_program_space): Use ui_out_emit_tuple.
> 	* probe.c (info_probes_for_ops): Use ui_out_emit_tuple.
> 	* osdata.c (info_osdata): Use ui_out_emit_tuple.
> 	* mi/mi-symbol-cmds.c (mi_cmd_symbol_list_lines): Use
> 	ui_out_emit_tuple.
> 	* mi/mi-main.c (print_one_inferior, list_available_thread_groups)
> 	(output_register, mi_cmd_data_read_memory)
> 	(mi_cmd_data_read_memory_bytes, mi_load_progress)
> 	(mi_cmd_trace_frame_collected): Use ui_out_emit_tuple.
> 	* mi/mi-cmd-var.c (mi_cmd_var_list_children, varobj_update_one):
> 	Use ui_out_emit_tuple.
> 	* mi/mi-cmd-stack.c (mi_cmd_stack_list_args): Use
> 	ui_out_emit_tuple.
> 	* mi/mi-cmd-info.c (mi_cmd_info_ada_exceptions)
> 	(mi_cmd_info_gdb_mi_command): Use ui_out_emit_tuple.
> 	* linux-thread-db.c (info_auto_load_libthread_db): Use
> 	ui_out_emit_tuple.
> 	* inferior.c (print_inferior): Use ui_out_emit_tuple.
> 	* gdb_bfd.c (print_one_bfd): Use ui_out_emit_tuple.
> 	* disasm.c (do_mixed_source_and_assembly_deprecated)
> 	(do_mixed_source_and_assembly): Use ui_out_emit_tuple.
> 	* cp-abi.c (list_cp_abis): Use ui_out_emit_tuple.
> 	* cli/cli-setshow.c (cmd_show_list): Use ui_out_emit_tuple.
> 	* breakpoint.c (print_one_breakpoint_location)
> 	(print_one_breakpoint): Use ui_out_emit_tuple.
> 	* auto-load.c (print_script, info_auto_load_cmd): Use
> 	ui_out_emit_tuple.
> 	* ada-tasks.c (print_ada_task_info): Use ui_out_emit_tuple.

LGTM.

Thanks,
Pedro Alves


  reply	other threads:[~2017-04-18 18:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14  2:23 [RFA 0/5] some cleanup removal for ui_out Tom Tromey
2017-04-14  2:23 ` [RFA 5/5] Use ui_out_emit_list Tom Tromey
2017-04-18 18:44   ` Pedro Alves
2017-04-14  2:23 ` [RFA 3/5] Use ui_out_emit_tuple in tracepoint.c Tom Tromey
2017-04-18 18:43   ` Pedro Alves
2017-04-14  2:23 ` [RFA 2/5] More uses of ui_out_emit_tuple Tom Tromey
2017-04-18 18:42   ` Pedro Alves
2017-04-19  2:42     ` Tom Tromey
2017-04-19  9:39       ` Pedro Alves
2017-04-14  2:24 ` [RFA 1/5] Use ui_out_emit_tuple Tom Tromey
2017-04-18 18:42   ` Pedro Alves [this message]
2017-04-14  2:42 ` [RFA 4/5] Use ui_out_emit_tuple in more places in MI Tom Tromey
2017-04-18 18:44   ` Pedro Alves
2017-04-22 15:44 ` [RFA 0/5] some cleanup removal for ui_out Tom Tromey
2017-04-27 14:51   ` Simon Marchi
2017-04-27 21:23     ` Tom Tromey

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=de26fc98-f0b1-f1e2-575e-733662cbce2e@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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