From: Frantisek Hrbata <fhrbata@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: jstancek@redhat.com, keescook@chromium.org,
peter.oberparleiter@de.ibm.com, rusty@rustcorp.com.au,
linux-arch@vger.kernel.org, arnd@arndb.de, mgahagan@redhat.com,
agospoda@redhat.com
Subject: [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version
Date: Fri, 23 Aug 2013 10:39:35 +0200 [thread overview]
Message-ID: <1377247176-13537-4-git-send-email-fhrbata@redhat.com> (raw)
In-Reply-To: <1377247176-13537-1-git-send-email-fhrbata@redhat.com>
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.
Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
---
kernel/gcov/Makefile | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/kernel/gcov/Makefile b/kernel/gcov/Makefile
index e97ca59..d57b712 100644
--- a/kernel/gcov/Makefile
+++ b/kernel/gcov/Makefile
@@ -1,3 +1,6 @@
ccflags-y := -DSRCTREE='"$(srctree)"' -DOBJTREE='"$(objtree)"'
-obj-$(CONFIG_GCOV_KERNEL) := base.o fs.o gcc_3_4.o
+obj-$(CONFIG_GCOV_KERNEL) := base.o fs.o
+
+obj-$(CONFIG_GCOV_KERNEL) += $(call cc-ifversion, -ge, 0407, gcc_4_7.o)
+obj-$(CONFIG_GCOV_KERNEL) += $(call cc-ifversion, -lt, 0407, gcc_3_4.o)
--
1.8.3.1
next prev parent reply other threads:[~2013-08-23 8:39 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 ` Frantisek Hrbata [this message]
2013-08-23 15:15 ` [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version 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
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=1377247176-13537-4-git-send-email-fhrbata@redhat.com \
--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=peter.oberparleiter@de.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
all inboxes | Powered by JetHome®