Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tim Wiederhake <tim.wiederhake@intel.com>
To: gdb-patches@sourceware.org
Cc: markus.t.metzger@intel.com, simon.marchi@polymtl.ca
Subject: [PATCH v4 00/12] btrace: Turn linked list of function call segments into vector
Date: Wed, 10 May 2017 11:47:00 -0000	[thread overview]
Message-ID: <1494416867-19612-1-git-send-email-tim.wiederhake@intel.com> (raw)

Hi all,

this series removes the extra list of btrace function call segments in struct
btrace_thread_info.  To achieve this, the doubly linked list of function call
segments in struct btrace_thread_info is replaced by a std::vector.

V1 of this series can be found here:
https://sourceware.org/ml/gdb-patches/2017-02/msg00482.html

V2 of this series can be found here:
https://sourceware.org/ml/gdb-patches/2017-05/msg00168.html

V3 of this series can be found here:
https://sourceware.org/ml/gdb-patches/2017-05/msg00202.html

Patches #1, #2 and #7 were LGTM'd by Simon.

Changes since V3:
* Patch #4: Replaced int with bool.  Added comment that btrace_function::number
  is 1-based.
* Patch #5: Simplified btrace_insn_cmp.
* Patch #6: Split line that had an assignment as a side effect. Added missing
  comment.
* Patch #9: Fixed patch title.
* Patch #10: Fixed patch title. Removed double assignment in ftrace_bridge_gaps.
* Patch #11: Moved comment to patch #6. Replaced "for (const auto& foo: ..."
  with "for (const unsigned int foo: ...".
* Patch #12: Added missing ChangeLog. Put "static" before "const". Changed
  comment of ftrace_find_call_by_number.

Regards,
Tim

Tim Wiederhake (12):
  btrace: Use std::vector in struct btrace_thread_information.
  btrace: Transfer ownership of pointers.
  btrace: Add btinfo to instruction interator.
  btrace: Use function segment index in call iterator.
  btrace: Use function segment index in insn iterator.
  btrace: Remove constant arguments.
  btrace: Remove struct btrace_thread_info::{begin,end}.
  btrace: Replace struct btrace_function::up.
  btrace: Remove struct btrace_function::flow.
  btrace: Replace struct btrace_function::segment.
  btrace: Remove bfun_s vector.
  btrace: Store function segments as objects.

 gdb/btrace.c                  | 850 +++++++++++++++++++++---------------------
 gdb/btrace.h                  |  64 ++--
 gdb/python/py-record-btrace.c |  12 +-
 gdb/record-btrace.c           |  30 +-
 4 files changed, 465 insertions(+), 491 deletions(-)

-- 
2.7.4


             reply	other threads:[~2017-05-10 11:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 11:47 Tim Wiederhake [this message]
2017-05-10 11:48 ` [PATCH v4 03/12] btrace: Add btinfo to instruction interator Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 10/12] btrace: Replace struct btrace_function::segment Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 06/12] btrace: Remove constant arguments Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 02/12] btrace: Transfer ownership of pointers Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 01/12] btrace: Use std::vector in struct btrace_thread_information Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 09/12] btrace: Remove struct btrace_function::flow Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 11/12] btrace: Remove bfun_s vector Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 04/12] btrace: Use function segment index in call iterator Tim Wiederhake
2017-05-11 10:02   ` Metzger, Markus T
2017-05-17  7:56     ` Wiederhake, Tim
2017-05-10 11:48 ` [PATCH v4 05/12] btrace: Use function segment index in insn iterator Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 07/12] btrace: Remove struct btrace_thread_info::{begin,end} Tim Wiederhake
2017-05-11 10:02   ` Metzger, Markus T
2017-05-10 11:48 ` [PATCH v4 12/12] btrace: Store function segments as objects Tim Wiederhake
2017-05-10 11:48 ` [PATCH v4 08/12] btrace: Replace struct btrace_function::up Tim Wiederhake
2017-05-10 14:46 ` [PATCH v4 00/12] btrace: Turn linked list of function call segments into vector Simon Marchi
2017-05-11  7:20   ` Wiederhake, Tim

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=1494416867-19612-1-git-send-email-tim.wiederhake@intel.com \
    --to=tim.wiederhake@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=simon.marchi@polymtl.ca \
    /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