From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org, markus.t.metzger@intel.com
Subject: Re: [PATCH v3 06/12] btrace: Remove constant arguments.
Date: Wed, 10 May 2017 02:45:00 -0000 [thread overview]
Message-ID: <05da714930334ac9ae083f28dcfa2fe0@polymtl.ca> (raw)
In-Reply-To: <1494312929-22749-7-git-send-email-tim.wiederhake@intel.com>
On 2017-05-09 02:55, Tim Wiederhake wrote:
> 2017-05-09 Tim Wiederhake <tim.wiederhake@intel.com>
>
> gdb/ChangeLog:
>
> * btrace.c (ftrace_new_function, ftrace_new_call, ftrace_new_tailcall,
> ftrace_new_return, ftrace_new_switch, ftrace_new_gap,
> ftrace_update_function): Remove arguments that implicitly were always
> BTINFO->END.
> (btrace_compute_ftrace_bts, ftrace_add_pt, btrace_compute_ftrace_pt):
> Don't pass BTINFO->END.
Looks good, just a few comments below.
> diff --git a/gdb/btrace.c b/gdb/btrace.c
> index cb30dcf..1bd11f0 100644
> --- a/gdb/btrace.c
> +++ b/gdb/btrace.c
> @@ -202,19 +202,19 @@ ftrace_function_switched (const struct
> btrace_function *bfun,
> return 0;
> }
>
> -/* Allocate and initialize a new branch trace function segment.
> +/* Allocate and initialize a new branch trace function segment at the
> end of
> + the trace.
> BTINFO is the branch trace information for the current thread.
> - PREV is the chronologically preceding function segment.
> MFUN and FUN are the symbol information we have for this function.
> */
>
> static struct btrace_function *
> ftrace_new_function (struct btrace_thread_info *btinfo,
> - struct btrace_function *prev,
> struct minimal_symbol *mfun,
> struct symbol *fun)
> {
> - struct btrace_function *bfun;
> + struct btrace_function *bfun, *prev;
>
> + prev = btinfo->end;
Note that we can now declare variables at the point we use it, and drop
the struct keyword, like:
btrace_function *prev = btinfo->end;
It's up to you, you can continue with your current style if you wish.
> bfun = XCNEW (struct btrace_function);
>
> bfun->msym = mfun;
> @@ -238,7 +238,7 @@ ftrace_new_function (struct btrace_thread_info
> *btinfo,
> }
>
> btinfo->functions.push_back (bfun);
> - return bfun;
> + return btinfo->end = bfun;
Err I'm really not a fan of assignment as a side effect.
> @@ -515,13 +510,13 @@ ftrace_new_gap (struct btrace_thread_info
> *btinfo,
> Return the chronologically latest function segment, never NULL. */
>
> static struct btrace_function *
> -ftrace_update_function (struct btrace_thread_info *btinfo,
> - struct btrace_function *bfun, CORE_ADDR pc)
> +ftrace_update_function (struct btrace_thread_info *btinfo, CORE_ADDR
> pc)
The comment of this function would need to be updated as well.
Thanks,
Simon
next prev parent reply other threads:[~2017-05-10 2:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 7:01 [PATCH v3 00/12] btrace: Turn linked list of function call segments into vector Tim Wiederhake
2017-05-09 7:01 ` [PATCH v3 07/12] btrace: Remove struct btrace_thread_info::{begin,end} Tim Wiederhake
2017-05-10 3:06 ` Simon Marchi
2017-05-09 7:01 ` [PATCH v3 01/12] btrace: Use std::vector in struct btrace_thread_information Tim Wiederhake
2017-05-09 12:10 ` Simon Marchi
2017-05-09 7:01 ` [PATCH v3 10/12] btrace: Replace struct btrace_thread_info::segment Tim Wiederhake
2017-05-10 4:14 ` Simon Marchi
2017-05-10 11:46 ` Wiederhake, Tim
2017-05-10 14:13 ` Simon Marchi
2017-05-09 7:01 ` [PATCH v3 05/12] btrace: Use function segment index in insn iterator Tim Wiederhake
2017-05-10 2:20 ` Simon Marchi
2017-05-10 11:46 ` Wiederhake, Tim
2017-05-09 7:01 ` [PATCH v3 04/12] btrace: Use function segment index in call iterator Tim Wiederhake
2017-05-09 12:50 ` Simon Marchi
2017-05-09 13:14 ` Wiederhake, Tim
2017-05-09 14:29 ` Simon Marchi
2017-05-09 7:01 ` [PATCH v3 12/12] btrace: Store function segments as objects Tim Wiederhake
2017-05-10 5:10 ` Simon Marchi
2017-05-10 11:46 ` Wiederhake, Tim
2017-05-10 14:16 ` Simon Marchi
2017-05-09 7:01 ` [PATCH v3 11/12] btrace: Remove bfun_s vector Tim Wiederhake
2017-05-10 4:27 ` Simon Marchi
2017-05-10 11:46 ` Wiederhake, Tim
2017-05-09 7:01 ` [PATCH v3 08/12] btrace: Replace struct btrace_thread_info::up Tim Wiederhake
2017-05-10 3:26 ` Simon Marchi
2017-05-10 11:46 ` Wiederhake, Tim
2017-05-09 7:01 ` [PATCH v3 06/12] btrace: Remove constant arguments Tim Wiederhake
2017-05-10 2:45 ` Simon Marchi [this message]
2017-05-10 11:46 ` Wiederhake, Tim
2017-05-09 7:01 ` [PATCH v3 02/12] btrace: Transfer ownership of pointers Tim Wiederhake
2017-05-09 12:21 ` Simon Marchi
2017-05-09 7:01 ` [PATCH v3 09/12] btrace: Remove struct btrace_thread_info::flow Tim Wiederhake
2017-05-10 3:46 ` Simon Marchi
2017-05-10 11:46 ` Wiederhake, Tim
2017-05-10 13:59 ` Simon Marchi
2017-05-09 7:01 ` [PATCH v3 03/12] btrace: Add btinfo to instruction interator 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=05da714930334ac9ae083f28dcfa2fe0@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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