linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Frantisek Hrbata <fhrbata@redhat.com>
Cc: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, jstancek@redhat.com,
	keescook@chromium.org, rusty@rustcorp.com.au,
	linux-arch@vger.kernel.org, mgahagan@redhat.com,
	agospoda@redhat.com
Subject: Re: [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version
Date: Sun, 25 Aug 2013 20:29:45 +0200	[thread overview]
Message-ID: <201308252029.45375.arnd@arndb.de> (raw)
In-Reply-To: <20130824194413.GB2365@localhost.localdomain>

On Saturday 24 August 2013, Frantisek Hrbata wrote:
> If I understand it correctly, this would mean that you will be able to use only
> one implementation of gcov format at the time. Meaning you will be able to get
> coverage data for module, but not for kernel if it was compiled with different
> gcc(gcda format). This is probably ok if you work only on your module, but I'm
> not sure this is generally the right approach. In this case I would probably
> rather see some support for more gcov formats at the same time(e.g. set of
> callback operations per gcov version). Again I'm probably missing something, but
> I still cannot see reason why to add such feature. If you want gcov support just
> compile your kernel and modules with the same gcc version(gcda format). But if
> this is really needed maybe it would be better to consider some parallel support
> for more gcov formats based on the gcov_info version.

The kernel is always built with exactly one version, including all the modules.
I don't see any reason whatsoever to support externally built modules with gcov,
in particular when they are not built with the system compiler.

	Arnd

  reply	other threads:[~2013-08-25 18:30 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  8:39 [RFC PATCH 0/4] add support for gcov format introduced in gcc 4.7 Frantisek Hrbata
2013-08-23  8:39 ` [RFC PATCH 1/4] gcov: move gcov structs definitions to a gcc version specific file Frantisek Hrbata
2013-08-23  8:39   ` Frantisek Hrbata
2013-08-23 15:09   ` Peter Oberparleiter
2013-08-23 15:09     ` Peter Oberparleiter
2013-08-23 16:50     ` Frantisek Hrbata
2013-08-23 16:50       ` Frantisek Hrbata
2013-08-26 12:17       ` Peter Oberparleiter
2013-08-23  8:39 ` [RFC PATCH 2/4] gcov: add support for gcc 4.7 gcov format Frantisek Hrbata
2013-08-23  8:39   ` Frantisek Hrbata
2013-08-23 15:12   ` Peter Oberparleiter
2013-08-23 21:00     ` Frantisek Hrbata
2013-08-26 12:45       ` Peter Oberparleiter
2013-08-27 13:41         ` Frantisek Hrbata
2013-08-27 13:41           ` Frantisek Hrbata
2013-08-23  8:39 ` [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version Frantisek Hrbata
2013-08-23  8:39   ` Frantisek Hrbata
2013-08-23 15:15   ` Peter Oberparleiter
2013-08-23 15:21     ` Peter Oberparleiter
2013-08-24 19:44       ` Frantisek Hrbata
2013-08-25 18:29         ` Arnd Bergmann [this message]
2013-08-26 14:14         ` Peter Oberparleiter
2013-08-27 13:34           ` Frantisek Hrbata
2013-08-28 13:46             ` Peter Oberparleiter
2013-08-28 13:54               ` Frantisek Hrbata
2013-08-28 13:54                 ` Frantisek Hrbata
2013-08-24 19:12     ` Frantisek Hrbata
2013-08-24 19:12       ` Frantisek Hrbata
2013-08-26 12:56       ` Peter Oberparleiter
2013-08-26 12:56         ` Peter Oberparleiter
2013-08-27 13:23         ` Frantisek Hrbata
2013-08-27 13:23           ` Frantisek Hrbata
2013-08-23  8:39 ` [RFC PATCH 4/4] kernel: add support for init_array constructors Frantisek Hrbata
2013-08-23  8:39   ` Frantisek Hrbata
2013-08-23 15:13   ` Peter Oberparleiter
2013-08-23 16:55     ` Frantisek Hrbata
2013-08-23 15:08 ` [RFC PATCH 0/4] add support for gcov format introduced in gcc 4.7 Peter Oberparleiter
2013-08-23 16:15   ` Frantisek Hrbata
2013-08-23 16:15     ` Frantisek Hrbata
2013-08-26 11:39     ` LF.Tan
2013-08-26 11:39       ` LF.Tan
2013-08-26 14:19       ` Peter Oberparleiter
2013-08-27  2:38         ` LF.Tan
2013-08-26 11:57     ` Peter Oberparleiter

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=201308252029.45375.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=agospoda@redhat.com \
    --cc=fhrbata@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgahagan@redhat.com \
    --cc=oberpar@linux.vnet.ibm.com \
    --cc=rusty@rustcorp.com.au \
    /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 NNTP newsgroup(s).