From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: Florian Meier <Florian.Meier@informatik.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcov: Support for >=gcc-6 missing
Date: Thu, 30 Jun 2016 14:13:38 +0200 [thread overview]
Message-ID: <b660a64f-d8f4-421d-b532-6c53a5c53d84@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACBfHbxw=krXJzV_VgfJJzL7Tc4On0hdGo4RBA4f7FSj_k7Y-Q@mail.gmail.com>
On 29.06.2016 16:58, Florian Meier wrote:
> Hello!
>
> I've noticed problems ("not executed"/ "file empty") with the gcov
> kernel support, when I'm using a gcc version >=6.
> For me, it seems like this is no technical reason, gcc 6 just was
> forgotten in the #ifdefs :).
>
> The following patch was tested with kernel 4.6.3 and gcc-6.1.1.
>
> I'm not 100% sure, that CGOV_COUNTERS=10 is correct, but the gcov
> output seemed reasonable.
Looking at the source of GCC 6's gcc/gcov-counter.def I don't see any
new counters added compared to GCC 5.1.0, so GCOV_COUNTERS=10 should
still be correct.
Given that the same situation could again arise with a potential GCC
7.x, adding a "__GNUC__ > 5 ||" to the condition of the existing #if
would be a longer-term solution. Could you re-post the patch with this
change?
>
> --- a/kernel/gcov/gcc_4_7.c 2016-05-16 00:43:13.000000000 +0200
> +++ b/kernel/gcov/gcc_4_7.c 13:41:41.726666665 +0200
> @@ -18,7 +18,9 @@
> #include <linux/vmalloc.h>
> #include "gcov.h"
>
> -#if __GNUC__ == 5 && __GNUC_MINOR__ >= 1
> +#if __GNUC__ == 6
> +#define GCOV_COUNTERS 10
> +#elif __GNUC__ == 5 && __GNUC_MINOR__ >= 1
> #define GCOV_COUNTERS 10
> #elif __GNUC__ == 4 && __GNUC_MINOR__ >= 9
> #define GCOV_COUNTERS 9
>
> Regards
> Florian Meier
>
--
Peter Oberparleiter
Linux on z Systems Development - IBM Germany
next prev parent reply other threads:[~2016-06-30 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 14:58 Florian Meier
2016-06-30 12:13 ` Peter Oberparleiter [this message]
2016-07-01 9:05 ` Florian Meier
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=b660a64f-d8f4-421d-b532-6c53a5c53d84@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=Florian.Meier@informatik.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®