From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename
Date: Mon, 27 Apr 2015 17:19:00 -0000 [thread overview]
Message-ID: <553E6F92.4020204@redhat.com> (raw)
In-Reply-To: <20150427164757.GA10548@host1.jankratochvil.net>
On 04/27/2015 05:47 PM, Jan Kratochvil wrote:
> On Mon, 27 Apr 2015 17:31:18 +0200, Pedro Alves wrote:
>> Hmm, but does it really make sense to add a "verbose" flag to
>> particular methods incrementally?
>>
>> It seems to me that "set debug compile" should enable verbosity in
>> in the plugin, for all methods. Which in turn suggests to me
>> that we should have a separate method in the plugin for toggling
>> verbosity?
>
> Are these questions or directions? I do not have an answer for the questions.
Both. I was curious on the reason why this was added as a flag
to a method, and on your thoughts, because, as I said, I seems to me
that that's not the best direction. So if there's no good reason,
I think it should indeed be made a separate method.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-04-27 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 20:34 Jan Kratochvil
2015-04-23 20:34 ` [PATCH v2 2/2] compile: Add 'set compile-gcc' Jan Kratochvil
2015-04-23 21:08 ` [PATCH v3 " Jan Kratochvil
2015-04-27 15:47 ` Pedro Alves
2015-04-27 17:54 ` Jan Kratochvil
2015-04-27 19:55 ` Pedro Alves
2015-04-27 15:31 ` [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename Pedro Alves
2015-04-27 16:48 ` Jan Kratochvil
2015-04-27 17:19 ` Pedro Alves [this message]
2015-04-27 17:52 ` Jan Kratochvil
2015-04-27 19:17 ` Pedro Alves
2015-04-27 20:44 ` Jan Kratochvil
2015-04-27 20:50 ` Jan Kratochvil
2015-04-27 21:49 ` Phil Muldoon
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=553E6F92.4020204@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).