linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: lkml <linux-kernel@vger.kernel.org>
Cc: oberpar@linux.vnet.ibm.com
Subject: [PATCH] gcov: support GCC 7.1
Date: Mon, 31 Oct 2016 10:35:15 +0100	[thread overview]
Message-ID: <8c4084fa-3885-29fe-5fc4-0d4ca199c785@suse.cz> (raw)

[-- Attachment #1: Type: text/plain, Size: 126 bytes --]

Hello.

Starting from GCC 7.1, __gcov_exit is a new symbol expected
to be implemented in a profiling runtime.

Thanks,
Martin

[-- Attachment #2: 0001-gcov-support-GCC-7.1.patch --]
[-- Type: text/x-patch, Size: 838 bytes --]

>From 84a106c16adc9591b546da7feb0fc539314e079d Mon Sep 17 00:00:00 2001
From: marxin <mliska@suse.cz>
Date: Fri, 30 Sep 2016 14:00:20 +0200
Subject: [PATCH] gcov: support GCC 7.1

Starting from GCC 7.1, __gcov_exit is a new symbol expected
to be implemented in a profiling runtime.

Signed-off-by: Martin Liska <mliska@suse.cz>
---
 kernel/gcov/base.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/kernel/gcov/base.c b/kernel/gcov/base.c
index 2f9df37..85dca5d 100644
--- a/kernel/gcov/base.c
+++ b/kernel/gcov/base.c
@@ -98,6 +98,12 @@ void __gcov_merge_icall_topn(gcov_type *counters, unsigned int n_counters)
 }
 EXPORT_SYMBOL(__gcov_merge_icall_topn);
 
+void __gcov_exit (void)
+{
+	/* Unused. */
+}
+EXPORT_SYMBOL(__gcov_exit);
+
 /**
  * gcov_enable_events - enable event reporting through gcov_event()
  *
-- 
2.10.1


             reply	other threads:[~2016-10-31  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31  9:35 Martin Liška [this message]
2016-11-09  9:21 ` [PATCH] gcov: support GCC 7.1 Peter Oberparleiter
2016-11-24 12:46   ` Martin Liška
2016-12-08 12:52     ` Peter Oberparleiter
2017-05-08 10:54       ` 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=8c4084fa-3885-29fe-5fc4-0d4ca199c785@suse.cz \
    --to=mliska@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oberpar@linux.vnet.ibm.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 NNTP newsgroup(s).