You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This documents goes over the steps to measure the size and runtime performance of MIP instrumented binaries using llvm-test-suite. For details on MIP, please see the patches at https://reviews.llvm.org/D104060.
llvm-project
Checkout the MIP patches in https://github.com/ellishg/llvm-project. To measure binary size fairly in MIP, we first need to extract the __llvm_mipdata section. Since there isn't an obious way to extract this section in llvm-test-suite, apply ExtractMapSection.patch to llvm-project. Now we can build normally.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To make the results a little more clear, I filtered for only the tests in MultiSource/Benchmarks/FreeBench/. I also only show the size differences of the .text section. It wouldn't be fair to compare the .data section since MIP injects data into the __llvm_mipraw section rather than the .data section.
To make the results a little more clear, I filtered for only the tests in
MultiSource/Benchmarks/FreeBench/
. I also only show the size differences of the.text
section. It wouldn't be fair to compare the.data
section since MIP injects data into the__llvm_mipraw
section rather than the.data
section.Base vs MIP
Text Size
Base vs
-fcs-profile-generate
Text Size