From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/5] gdb: change jit_debug to a bool
Date: Fri, 8 Jan 2021 23:29:50 -0500 [thread overview]
Message-ID: <c31fd763-f692-440a-b148-9b9b7bc20cc5@polymtl.ca> (raw)
In-Reply-To: <20210109042816.4140840-1-simon.marchi@polymtl.ca>
Hi Mihails,
Since you deal with JIT a lot, would you mind giving this patch a look?
Thanks!
Simon
On 2021-01-08 11:28 p.m., Simon Marchi wrote:
> gdb/ChangeLog:
>
> * jit.c (jit_debug): Change type to bool.
> (_initialize_jit): Adjust.
>
> Change-Id: Ic2b1eec28eafe8ccb2899f38ddc91ba9703cb38e
> ---
> gdb/jit.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/gdb/jit.c b/gdb/jit.c
> index ad951cdfbb52..474ba838b86b 100644
> --- a/gdb/jit.c
> +++ b/gdb/jit.c
> @@ -58,9 +58,9 @@ static void jit_inferior_exit_hook (struct inferior *inf);
>
> static struct gdbarch_data *jit_gdbarch_data;
>
> -/* Non-zero if we want to see trace of jit level stuff. */
> +/* True if we want to see trace of jit level stuff. */
>
> -static unsigned int jit_debug = 0;
> +static bool jit_debug = false;
>
> static void
> show_jit_debug (struct ui_file *file, int from_tty,
> @@ -1251,13 +1251,13 @@ _initialize_jit ()
> {
> jit_reader_dir = relocate_gdb_directory (JIT_READER_DIR,
> JIT_READER_DIR_RELOCATABLE);
> - add_setshow_zuinteger_cmd ("jit", class_maintenance, &jit_debug,
> - _("Set JIT debugging."),
> - _("Show JIT debugging."),
> - _("When non-zero, JIT debugging is enabled."),
> - NULL,
> - show_jit_debug,
> - &setdebuglist, &showdebuglist);
> + add_setshow_boolean_cmd ("jit", class_maintenance, &jit_debug,
> + _("Set JIT debugging."),
> + _("Show JIT debugging."),
> + _("When non-zero, JIT debugging is enabled."),
> + NULL,
> + show_jit_debug,
> + &setdebuglist, &showdebuglist);
>
> gdb::observers::inferior_created.attach (jit_inferior_created_hook);
> gdb::observers::inferior_execd.attach (jit_inferior_created_hook);
>
next prev parent reply other threads:[~2021-01-09 4:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 4:28 Simon Marchi via Gdb-patches
2021-01-09 4:28 ` [PATCH 2/5] gdb: convert jit to new-style debug macros Simon Marchi via Gdb-patches
2021-01-11 21:18 ` Tom Tromey
2021-01-11 21:20 ` Simon Marchi via Gdb-patches
2021-01-09 4:28 ` [PATCH 3/5] gdb: convert aarch64 " Simon Marchi via Gdb-patches
2021-01-09 4:31 ` Simon Marchi via Gdb-patches
2021-01-11 13:18 ` Luis Machado via Gdb-patches
2021-01-11 21:30 ` Simon Marchi via Gdb-patches
2021-01-11 21:50 ` Luis Machado via Gdb-patches
2021-01-11 21:54 ` Simon Marchi via Gdb-patches
2021-01-09 4:28 ` [PATCH 4/5] gdb: convert solib-aix " Simon Marchi via Gdb-patches
2021-01-11 21:19 ` Tom Tromey
2021-01-11 21:32 ` Simon Marchi via Gdb-patches
2021-01-09 4:28 ` [PATCH 5/5] gdb: convert arc " Simon Marchi via Gdb-patches
2021-01-09 4:37 ` Simon Marchi via Gdb-patches
2021-01-13 15:35 ` Shahab Vahedi via Gdb-patches
2021-01-09 4:29 ` Simon Marchi via Gdb-patches [this message]
2021-01-11 21:17 ` [PATCH 1/5] gdb: change jit_debug to a bool Tom Tromey
2021-01-11 21:19 ` Simon Marchi via Gdb-patches
2021-01-13 14:32 ` Shahab Vahedi via Gdb-patches
2021-01-13 15:49 ` Simon Marchi via Gdb-patches
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=c31fd763-f692-440a-b148-9b9b7bc20cc5@polymtl.ca \
--to=gdb-patches@sourceware.org \
--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