From: Frantisek Hrbata <fhrbata@redhat.com>
To: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, jstancek@redhat.com,
keescook@chromium.org, rusty@rustcorp.com.au,
linux-arch@vger.kernel.org, arnd@arndb.de, mgahagan@redhat.com,
agospoda@redhat.com
Subject: Re: [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version
Date: Sat, 24 Aug 2013 21:12:27 +0200 [thread overview]
Message-ID: <20130824191227.GA2365@localhost.localdomain> (raw)
In-Reply-To: <52177C87.4090003@linux.vnet.ibm.com>
On Fri, Aug 23, 2013 at 05:15:19PM +0200, Peter Oberparleiter wrote:
> On 23.08.2013 10:39, Frantisek Hrbata wrote:
> > Compile the correct gcov implementation file for a specific gcc version. In
> > the future, if another file is added, the conditions will need to be somehow
> > adjusted to if-elif-else case, but at this point the simple cc-ifversion should
> > be enough.
>
> Looks good, though I think this could be merged into the main 4.7 format patch,
> since without it, the 4.7 code will never be reached.
Sure, I can merge these two patches.
>
> Also it is my understanding that there are some distribution-specific versions
> of GCC that include the 4.7. gcov format code but report GCC version 4.6. With
> the auto-detection code implemented like this, gcov-kernel won't work correctly.
> For that purpose I've implemented a configuration option to allow users to
> force a specific version of gcov format.
Ah, I was not aware of this inconsistency in versioning. This raises a question
if it would not be better to deal directly with version in the gcov_info
instead of these config options. This would of course mean some kind of gcov
operations callbacks per gcov version(you already mentioned the file
operations approach).
>
> I'm attaching the corresponding patch below:
>
> ---
> kernel: gcov: make data format configurable
>
> Make the format of the generated gcov data configurable. This may be
> required for example for pre-4.7 GCCs that contain the 4.7 gcov data
> format changes.
>
> Signed-off-by: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
> ---
> kernel/gcov/Kconfig | 30 ++++++++++++++++++++++++++++++
> kernel/gcov/Makefile | 21 +++++++++++++++++++--
> 2 files changed, 49 insertions(+), 2 deletions(-)
>
> --- a/kernel/gcov/Kconfig
> +++ b/kernel/gcov/Kconfig
> @@ -46,4 +46,34 @@ config GCOV_PROFILE_ALL
> larger and run slower. Also be sure to exclude files from profiling
> which are not linked to the kernel image to prevent linker errors.
>
> +choice
> + prompt "Specify GCOV format"
> + depends on GCOV_KERNEL
> + default GCOV_FORMAT_AUTODETECT
> + ---help---
> + The gcov format is usually determined by the GCC version, but there are
> + exceptions where format changes are integrated in lower-version GCCs.
> + In such a case use this option to adjust the format used in the kernel
> + accordingly.
> +
> + If unsure, choose "Autodetect".
> +
> +config GCOV_FORMAT_AUTODETECT
> + bool "Autodetect"
> + ---help---
> + Select this option to use the format that corresponds to your GCC
> + version.
> +
> +config GCOV_FORMAT_3_4
> + bool "GCC 3.4 format"
> + ---help---
> + Select this option to use the format defined by GCC 3.4.
> +
> +config GCOV_FORMAT_4_7
> + bool "GCC 4.7 format"
> + ---help---
> + Select this option to use the format defined by GCC 4.7.
> +
> +endchoice
> +
> endmenu
> --- a/kernel/gcov/Makefile
> +++ b/kernel/gcov/Makefile
> @@ -1,5 +1,22 @@
> ccflags-y := -DSRCTREE='"$(srctree)"' -DOBJTREE='"$(objtree)"'
>
> +# if-lt
> +# Usage VAR := $(call if-lt, $(a), $(b))
> +# Returns 1 if (a < b)
> +if-lt = $(shell [ $(1) -lt $(2) ] && echo 1)
> +
> +ifeq ($(CONFIG_GCOV_FORMAT_3_4),y)
> + cc-ver := 0304
> +else ifeq ($(CONFIG_GCOV_FORMAT_4_7),y)
> + cc-ver := 0407
> +else
> + cc-ver := $(call cc-version)
> +endif
> +
> obj-$(CONFIG_GCOV_KERNEL) := base.o fs.o
> -obj-$(CONFIG_GCOV_KERNEL) += $(call cc-ifversion, -lt, 0407, gcc_3_4.o)
> -obj-$(CONFIG_GCOV_KERNEL) += $(call cc-ifversion, -ge, 0407, gcc_4_7.o)
> +
> +ifeq ($(call if-lt, $(cc-ver), 0407),1)
> + obj-$(CONFIG_GCOV_KERNEL) += gcc_3_4.o
> +else
> + obj-$(CONFIG_GCOV_KERNEL) += gcc_4_7.o
> +endif
>
>
> --
> Peter Oberparleiter
> Linux on System z Development - IBM Germany
>
--
Frantisek Hrbata
next prev parent reply other threads:[~2013-08-24 19:12 UTC|newest]
Thread overview: 31+ 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 15:09 ` Peter Oberparleiter
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 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-23 8:39 ` [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version 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
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-24 19:12 ` Frantisek Hrbata [this message]
2013-08-26 12:56 ` Peter Oberparleiter
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 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-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=20130824191227.GA2365@localhost.localdomain \
--to=fhrbata@redhat.com \
--cc=agospoda@redhat.com \
--cc=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.