Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
	markus.t.metzger@intel.com
Subject: Re: [PATCH 3/7] btrace: Use binary search to find instruction.
Date: Thu, 27 Oct 2016 14:28:00 -0000	[thread overview]
Message-ID: <32eeec01cc2ddc61dcb90caab5a6e645@polymtl.ca> (raw)
In-Reply-To: <1477549711-2603-4-git-send-email-tim.wiederhake@intel.com>

On 2016-10-27 02:28, Tim Wiederhake wrote:
> Currently, btrace_find_insn_by_number will iterate over all function 
> call
> segments to find the one that contains the needed instruction.  This 
> linear
> search is too slow for the upcoming Python bindings that will use this
> function to access instructions.  This patch introduces a vector in 
> struct
> btrace_thread_info that holds pointers to all recorded function 
> segments and
> allows to use binary search.
> 
> The proper solution is to turn the underlying tree into a vector of 
> objects
> and use indices for access.  This requires more work.  A patch set is
> currently being worked on and will be published later.

Hi Tim,

Unless you expect to backport this patch in the 7.12 branch (which I 
don't think is the case here), you can use C++ standard containers and 
functions.  Specifically, std::vector instead of DEF_VEC, and probably 
std::lower_bound (if I understand correctly what the code is doing).

Also, since we now have btrace_function pointers in a sorted vector, do 
we still need them to be linked together as a linked list?

Simon


  reply	other threads:[~2016-10-27 14:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27  6:29 [PATCH 0/7] Python bindings for btrace recordings Tim Wiederhake
2016-10-27  6:29 ` [PATCH 5/7] python: Implement btrace Python bindings for record history Tim Wiederhake
2016-10-27  6:29 ` [PATCH 2/7] btrace: Export btrace_decode_error function Tim Wiederhake
2016-10-27  6:29 ` [PATCH 4/7] python: Create Python bindings for record history Tim Wiederhake
2016-10-27 15:53   ` Simon Marchi
2016-10-28 14:12     ` Wiederhake, Tim
2016-10-27  6:29 ` [PATCH 7/7] Add documentation for new instruction record Python bindings Tim Wiederhake
2016-10-27 15:02   ` Eli Zaretskii
2016-10-27 16:10   ` Simon Marchi
2016-10-27  6:29 ` [PATCH 6/7] python: Add tests for " Tim Wiederhake
2016-10-27 15:59   ` Simon Marchi
2016-10-28 13:49     ` Wiederhake, Tim
2016-10-28 17:47       ` Simon Marchi
2016-10-27  6:29 ` [PATCH 3/7] btrace: Use binary search to find instruction Tim Wiederhake
2016-10-27 14:28   ` Simon Marchi [this message]
2016-11-02 10:01     ` Wiederhake, Tim
2016-11-02 11:24       ` Simon Marchi
2016-10-27  6:29 ` [PATCH 1/7] btrace: Count gaps as one instruction explicitly Tim Wiederhake

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=32eeec01cc2ddc61dcb90caab5a6e645@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=palves@redhat.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