From: Jan Hubicka <hubicka@ucw.cz>
To: Nathan Sidwell <nathan@acm.org>
Cc: Aaron Conole <aconole@redhat.com>,
gcc-patches@gcc.gnu.org, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH v2] gcov: Runtime configurable destination output
Date: Wed, 04 May 2016 15:25:00 -0000 [thread overview]
Message-ID: <20160504152542.GC24625@kam.mff.cuni.cz> (raw)
In-Reply-To: <6ab05137-7f81-7024-6c21-640dccb16766@acm.org>
> On 04/29/16 11:08, Aaron Conole wrote:
>
> >Perhaps I've poorly explained what I want. I want to be able to pipe
> >gcov error messages to a different file for post-processing / reporting
> >elsewhere. I don't want them mixed with the application's messages. Do
> >you think this kind of generic flexibility is not a good thing, when it
> >comes at such little cost?
>
> Thanks for clarifying your rationale. I'm not convinced, but I'm
> not (yet) saying no.
>
> Jan, do you have any thoughts?
I can imagine this to be useful - if your application is outputting stuff into
error output during its training run, it may be quite disturbing having gcov
diagnostics randomly mixed in. (in particular I run myself into cases missing
the diagnostics) So I am fine with the feature.
Honza
>
> nathan
next prev parent reply other threads:[~2016-05-04 15:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 21:52 Aaron Conole
2016-04-15 19:02 ` Aaron Conole
2016-04-27 20:59 ` Aaron Conole
2016-04-28 13:25 ` Nathan Sidwell
2016-04-29 15:08 ` Aaron Conole
2016-05-04 15:22 ` Nathan Sidwell
2016-05-04 15:25 ` Jan Hubicka [this message]
2016-05-06 13:18 ` Nathan Sidwell
2016-05-19 18:40 ` Aaron Conole
2016-05-19 19:25 ` Jeff Law
2016-05-19 23:14 ` Nathan Sidwell
2016-05-20 1:11 ` Jeff Law
2016-05-19 23:17 ` Nathan Sidwell
2016-05-23 18:16 ` Aaron Conole
2016-06-03 15:00 ` H.J. Lu
2016-06-03 15:31 ` Aaron Conole
2016-06-04 12:12 ` Aaron Conole
2016-06-06 15:25 ` Nathan Sidwell
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=20160504152542.GC24625@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=aconole@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
/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).