profraw: raw profile version mismatch while collecting converage

[sugamadhiakri]

First I followed the instructions with LLVM 19 and ran into #5 then I installed LLVM-18 and ran into #4 .

I used the following command:

sudo usermod -aG kvm $USER
newgrp kvm

Now, when trying to execute this command chain:

mkdir -p $MCDC_HOME/analysis
mv profraw $MCDC_HOME/analysis
cd $MCDC_HOME/analysis

llvm-profdata merge profraw -o profdata
llvm-cov show --show-mcdc                                                      \
              --show-mcdc-summary                                              \
              --show-region-summary=false                                      \
              --show-branch-summary=false                                      \
              --format=html                                                    \
              -show-directory-coverage                                         \
              -output-dir=html-coverage-reports                                \
              -instr-profile profdata                                          \
              $MCDC_HOME/linux/vmlinux

I am getting the following error:

[whentojump]

Make sure you are using the same toolchain to produce and to consume the profile.

From what I can see you built the kernel with LLVM 18, but your invocations of llvm-profdata and llvm-cov look like 19.

llvm-profdata --version
llvm-cov --version

[sugamadhiakri]

Thank you. I looked into the PATH and it didn't have the path to LLVM 18. After updating the path, I was able to get the coverage reports. Are there any tasks for me now? Should I look into your reply at #5 ?

[whentojump]

Sounds great! Hopefully you've had a big picture now. You are always encouraged to rethink this whole process, explore and ask if there's anything unclear.

Are there any tasks for me now? Should I look into your reply at #5 ?

Yeah please do that. Depending on your expertise and interests, you may also start fixing some LLVM bugs. If you prefer the latter, let's talk more in emails.

cc @darko-marinov

[sugamadhiakri]

Hi Wentao, How should I start working on fixing LLVM bugs? I want to explore this and meanwhile I will follow your instructions on reducing the binary size. Also, is there a platform being used to communicate asynchronously other than email in this project? (Assuming there are other people working alongside you) I would love to be in the loop. Thanks

…

On Tue, Jun 25, 2024 at 11:13 AM Wentao Zhang ***@***.***> wrote: Sounds great! Hopefully you've had a big picture now. You are always encouraged to rethink this whole process, explore and ask if there's anything unclear. Are there any tasks for me now? Should I look into your reply at #5 <#5> ? Yeah please do that. Depending on your expertise and interests, you may also start fixing some LLVM bugs. If you prefer the latter, let's talk more in emails. cc @darko-marinov <https://github.com/darko-marinov> — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGURQLQBLF2YZAC2SOWRV7TZJD5ZTAVCNFSM6AAAAABJ3AUXCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYGAYDSNJQGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[whentojump]

The issue in the original post is addressed. Let's discuss your plan in the other channel.