Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org,  markus.t.metzger@intel.com,
	 brobecker@adacore.com
Subject: Re: [PATCH v2 6/8] Python: Move and rename gdb.BtraceInstruction
Date: Fri, 21 Apr 2017 15:21:00 -0000	[thread overview]
Message-ID: <86tw5hzubi.fsf@gmail.com> (raw)
In-Reply-To: <1492771786-26372-7-git-send-email-tim.wiederhake@intel.com> (Tim	Wiederhake's message of "Fri, 21 Apr 2017 12:49:44 +0200")

Tim Wiederhake <tim.wiederhake@intel.com> writes:

> 2017-04-21  Tim Wiederhake  <tim.wiederhake@intel.com>
>
> gdb/ChangeLog:
> 	* python/py-record-btrace.c (BTPY_REQUIRE_VALID_INSN): Remove.
> 	(btpy_object, btpy_insn_type, btpy_new): Remove.
> 	(btpy_list_object): Use gdb.RecordInstruction type instead of
> 	gdb.BtraceInstruction type.
> 	(btrace_insn_from_recpy_insn): New function.
> 	(btpy_insn_or_gap_new): Adjust comment. Use recpy_insn_new instead of
> 	btpy_new.
> 	(btpy_call_new, btpy_list_item): Do not use btpy_new anymore.
> 	(btpy_number, btpy_hash, btpy_call_level, btpy_call_symbol,
> 	btpy_call_instructions, btpy_call_up, btpy_call_prev_sibling,
> 	btpy_call_next_sibling, btpy_richcompare): Use recpy_element_object
> 	instead of btpy_object.
> 	(btpy_insn_sal, btpy_insn_pc, btpy_insn_size, btpy_insn_is_speculative,
> 	btpy_insn_data, btpy_insn_decode): Rename to ...
> 	(recpy_bt_insn_sal, recpy_bt_insn_pc, recpy_bt_insn_size,
> 	recpy_bt_insn_is_speculative, recpy_bt_insn_data,
> 	recpy_bt_insn_decode): This.  Also, use new helper functions.
> 	(btpy_list_position, recpy_bt_goto): Use recpy_element_object and
> 	recpy_insn_type.
> 	(btpy_insn_getset): Remove.
> 	(gdbpy_initialize_btrace): Remove code to initialize
> 	gdb.BtraceInstruction.  Use recpy_element_object.
> 	* python/py-record-btrace.h (recpy_bt_insn_number, recpy_bt_insn_sal,
> 	recpy_bt_insn_pc, recpy_bt_insn_data, recpy_bt_insn_decoded,
> 	recpy_bt_insn_size, recpy_bt_insn_is_speculative): New export.
> 	* python/py-record.c (recpy_insn_type): New static object.
> 	(recpy_insn_new, recpy_insn_sal, recpy_insn_pc, recpy_insn_data,
> 	recpy_insn_decoded, recpy_insn_size, recpy_insn_is_speculative,
> 	recpy_element_number, recpy_element_hash, recpy_element_richcompare):
> 	New function.
> 	(recpy_insn_getset): New static object.
> 	(gdbpy_initialize_record): Initialize gdb.RecordInstruction.
> 	* python/py-record.h (recpy_element_object): New typedef.
> 	(recpy_insn_type, recpy_insn_new): New export.

Patch is good to me.

-- 
Yao (齐尧)


  parent reply	other threads:[~2017-04-21 15:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 10:50 [PATCH v2 0/8] Python bindings for GDB record Tim Wiederhake
2017-04-21 10:50 ` [PATCH v2 2/8] Python: Fix exception handling in py-record-btrace.c Tim Wiederhake
2017-04-21 18:08   ` Yao Qi
2017-04-27 16:35   ` Pedro Alves
2017-04-21 10:50 ` [PATCH v2 5/8] Python: Introduce gdb.RecordGap class Tim Wiederhake
2017-04-21 12:25   ` Eli Zaretskii
2017-04-21 14:50   ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 3/8] Python: Use correct ptid in btrace recording Tim Wiederhake
2017-04-21 14:49   ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 6/8] Python: Move and rename gdb.BtraceInstruction Tim Wiederhake
2017-04-21 12:23   ` Eli Zaretskii
2017-04-21 15:21   ` Yao Qi [this message]
2017-04-21 10:50 ` [PATCH v2 1/8] Python: Fix indentation in py-record-btrace.c Tim Wiederhake
2017-04-21 10:50 ` [PATCH v2 7/8] Python: Move and rename gdb.BtraceFunction Tim Wiederhake
2017-04-21 12:22   ` Eli Zaretskii
2017-04-21 16:41   ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 4/8] Python: Remove ptid from gdb.Record interface Tim Wiederhake
2017-04-21 12:20   ` Eli Zaretskii
2017-04-21 10:50 ` [PATCH v2 8/8] Python: Introduce gdb.Instruction class Tim Wiederhake
2017-04-21 12:19   ` Eli Zaretskii
2017-04-24  5:34     ` Wiederhake, Tim
2017-04-21 18:10   ` 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=86tw5hzubi.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=tim.wiederhake@intel.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