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 02/11] btrace: Add btinfo to instruction interator.
Date: Mon, 08 May 2017 08:13:00 -0000	[thread overview]
Message-ID: <1494231185-4709-3-git-send-email-tim.wiederhake@intel.com> (raw)
In-Reply-To: <1494231185-4709-1-git-send-email-tim.wiederhake@intel.com>

This will serve as the access path to the vector of function segments once
the FUNCTION pointer in struct btrace_insn_iterator is removed.

2017-05-08  Tim Wiederhake  <tim.wiederhake@intel.com>

gdb/ChangeLog:

	* btrace.c (btrace_insn_begin, btrace_insn_end,
	btrace_find_insn_by_number): Add btinfo to iterator.
	* btrace.h (struct btrace_insn_iterator): Add btinfo.

---
 gdb/btrace.c | 3 +++
 gdb/btrace.h | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/gdb/btrace.c b/gdb/btrace.c
index b316344..d701f54 100644
--- a/gdb/btrace.c
+++ b/gdb/btrace.c
@@ -2295,6 +2295,7 @@ btrace_insn_begin (struct btrace_insn_iterator *it,
   if (bfun == NULL)
     error (_("No trace."));
 
+  it->btinfo = btinfo;
   it->function = bfun;
   it->index = 0;
 }
@@ -2320,6 +2321,7 @@ btrace_insn_end (struct btrace_insn_iterator *it,
   if (length > 0)
     length -= 1;
 
+  it->btinfo = btinfo;
   it->function = bfun;
   it->index = length;
 }
@@ -2523,6 +2525,7 @@ btrace_find_insn_by_number (struct btrace_insn_iterator *it,
       break;
     }
 
+  it->btinfo = btinfo;
   it->function = bfun;
   it->index = number - bfun->insn_offset;
   return 1;
diff --git a/gdb/btrace.h b/gdb/btrace.h
index 07ed10c..f912b04 100644
--- a/gdb/btrace.h
+++ b/gdb/btrace.h
@@ -193,6 +193,9 @@ DEF_VEC_P (btrace_fun_p);
 /* A branch trace instruction iterator.  */
 struct btrace_insn_iterator
 {
+  /* The branch trace information for this thread.  Will never be NULL.  */
+  const struct btrace_thread_info *btinfo;
+
   /* The branch trace function segment containing the instruction.
      Will never be NULL.  */
   const struct btrace_function *function;
-- 
2.7.4


  parent 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 [PATCH v2 00/11] btrace: Turn linked list of function call segments into vector 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 06/11] btrace: Remove struct btrace_thread_info::{begin,end} Tim Wiederhake
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 05/11] btrace: Remove constant arguments 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 03/11] btrace: Use function segment index in call 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 04/11] btrace: Use function segment index in insn iterator Tim Wiederhake
2017-05-08  8:13 ` [PATCH v2 08/11] btrace: Remove struct btrace_thread_info::flow Tim Wiederhake
2017-05-08  8:13 ` Tim Wiederhake [this message]
2017-05-08  8:13 ` [PATCH v2 11/11] btrace: Store function segments as objects 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-3-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