From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Peter Oberparleiter <oberpar@linux.ibm.com>,
Nathan Chancellor <nathan@kernel.org>,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
Fangrui Song <maskray@google.com>,
Prasad Sodagudi <psodagud@quicinc.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] gcov: re-fix clang-11+ support
Date: Wed, 7 Apr 2021 14:21:21 -0700 [thread overview]
Message-ID: <20210407142121.677e971e9e5dc85643441811@linux-foundation.org> (raw)
In-Reply-To: <20210407185456.41943-2-ndesaulniers@google.com>
On Wed, 7 Apr 2021 11:54:55 -0700 Nick Desaulniers <ndesaulniers@google.com> wrote:
> LLVM changed the expected function signature for
> llvm_gcda_emit_function() in the clang-11 release. Users of clang-11 or
> newer may have noticed their kernels producing invalid coverage
> information:
>
> $ llvm-cov gcov -a -c -u -f -b <input>.gcda -- gcno=<input>.gcno
> 1 <func>: checksum mismatch, \
> (<lineno chksum A>, <cfg chksum B>) != (<lineno chksum A>, <cfg chksum C>)
> 2 Invalid .gcda File!
> ...
>
> Fix up the function signatures so calling this function interprets its
> parameters correctly and computes the correct cfg checksum. In
> particular, in clang-11, the additional checksum is no longer optional.
Which tree is this against? I'm seeing quite a lot of rejects against
Linus's current.
next prev parent reply other threads:[~2021-04-07 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 18:54 [PATCH 0/2] gcov: re-fix clang-11 support Nick Desaulniers
2021-04-07 18:54 ` [PATCH 1/2] gcov: re-fix clang-11+ support Nick Desaulniers
2021-04-07 19:51 ` Nathan Chancellor
2021-04-07 21:21 ` Andrew Morton [this message]
2021-04-07 21:28 ` Nick Desaulniers
2021-04-07 22:26 ` Andrew Morton
2021-04-08 18:46 ` [PATCH v2] " Nick Desaulniers
2021-04-07 18:54 ` [PATCH 2/2] gcov: re-drop support for clang-10 Nick Desaulniers
2021-04-07 19:07 ` Fangrui Song
2021-04-07 19:51 ` Nathan Chancellor
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=20210407142121.677e971e9e5dc85643441811@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maskray@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oberpar@linux.ibm.com \
--cc=psodagud@quicinc.com \
--cc=stable@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 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.