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
Subject: [PATCH v2 00/11] btrace: Turn linked list of function call segments into vector
Date: Mon, 08 May 2017 08:13:00 -0000	[thread overview]
Message-ID: <1494231185-4709-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 (GDB) vector.  In some
instances, struct btrace_thread_info is initialized by memset'ing it to 0x00,
so we can't use std::vector (yet).

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

The patches are differently ordered in comparison to V1, removing the necessity
of the "big squash".

Regards,
Tim


Tim Wiederhake (11):
  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_thread_info::up.
  btrace: Remove struct btrace_thread_info::flow.
  btrace: Replace struct btrace_thread_info::segment.
  btrace: Remove bfun_s vector.
  btrace: Store function segments as objects.

 gdb/btrace.c                  | 852 +++++++++++++++++++++---------------------
 gdb/btrace.h                  |  62 ++-
 gdb/python/py-record-btrace.c |  12 +-
 gdb/record-btrace.c           |  32 +-
 4 files changed, 472 insertions(+), 486 deletions(-)

-- 
2.7.4


             reply	other threads:[~2017-05-08  8:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08  8:13 Tim Wiederhake [this message]
2017-05-08  8:13 ` [PATCH v2 07/11] btrace: Replace struct btrace_thread_info::up Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 06/11] btrace: Remove struct btrace_thread_info::{begin,end} Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 09/11] btrace: Replace struct btrace_thread_info::segment Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 01/11] btrace: Transfer ownership of pointers Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 05/11] btrace: Remove constant arguments Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 04/11] btrace: Use function segment index in insn iterator Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 10/11] btrace: Remove bfun_s vector Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 03/11] btrace: Use function segment index in call iterator Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 11/11] btrace: Store function segments as objects Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 02/11] btrace: Add btinfo to instruction interator Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 08/11] btrace: Remove struct btrace_thread_info::flow Tim Wiederhake
2017-05-08  9:03 ` [PATCH v2 00/11] btrace: Turn linked list of function call segments into vector Yao Qi via gdb-patches
2017-05-08 10:23   ` 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=1494231185-4709-1-git-send-email-tim.wiederhake@intel.com \
    --to=tim.wiederhake@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@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