Displaying 6 results from an estimated 6 matches for "llvm_profile_merge_pool_size".
2017 Jun 27
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...gt;>>> 3. The generated profile information takes up a lot of space: llc
>>>> generates a 90MB profraw file.
>>>
>>> I don't have any ideas about how to fix this. You can decrease the
>>> space overhead for raw profiles by altering
>>> LLVM_PROFILE_MERGE_POOL_SIZE from 4 to a lower value.
>>
>> Disk space is cheap, but the I/O takes a long time. I guess it's
>> specifically bad for LLVM's "make check", maybe not so bad for other
>> cases.
>
> You can speed up "make check" a bit by using non-instrum...
2017 Jun 27
2
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...profile information takes up a lot of space:
>>>>> llc generates a 90MB profraw file.
>>>>
>>>> I don't have any ideas about how to fix this. You can decrease
>>>> the space overhead for raw profiles by altering
>>>> LLVM_PROFILE_MERGE_POOL_SIZE from 4 to a lower value.
>>>
>>> Disk space is cheap, but the I/O takes a long time. I guess
>>> it's specifically bad for LLVM's "make check", maybe not so bad
>>> for other cases.
>>
>> You can speed up "make...
2017 Jun 19
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...01
> <http://llvm.org/PR33501>.
>
>> 3. The generated profile information takes up a lot of space: llc
>> generates a 90MB profraw file.
>
> I don't have any ideas about how to fix this. You can decrease the
> space overhead for raw profiles by altering
> LLVM_PROFILE_MERGE_POOL_SIZE from 4 to a lower value.
Disk space is cheap, but the I/O takes a long time. I guess it's
specifically bad for LLVM's "make check", maybe not so bad for other cases.
>> 4. When prepare-code-coverage-artifact.py invokes llvm-profdata for
>> the profiles generated b...
2017 Jun 27
2
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...;>>
>>> 3. The generated profile information takes up a lot of space: llc
>>> generates a 90MB profraw file.
>>>
>>>
>>> I don't have any ideas about how to fix this. You can decrease the space
>>> overhead for raw profiles by altering LLVM_PROFILE_MERGE_POOL_SIZE from
>>> 4 to a lower value.
>>>
>>>
>>> Disk space is cheap, but the I/O takes a long time. I guess it's
>>> specifically bad for LLVM's "make check", maybe not so bad for other cases.
>>>
>>>
>>> You can sp...
2017 Jun 27
4
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...t;>
>>>>>>> 3. The generated profile information takes up a lot of space: llc generates a 90MB profraw file.
>>>>>>
>>>>>> I don't have any ideas about how to fix this. You can decrease the space overhead for raw profiles by altering LLVM_PROFILE_MERGE_POOL_SIZE from 4 to a lower value.
>>>>>
>>>>> Disk space is cheap, but the I/O takes a long time. I guess it's specifically bad for LLVM's "make check", maybe not so bad for other cases.
>>>>
>>>> You can speed up "make check&qu...
2017 Jun 17
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
I've started looking at the state of code coverage recently; we figured
LLVM itself would be a good test to figure out how mature it is, so I
gave it a shot. My experience:
1. You have to specify -DLLVM_USE_LINKER=gold (or maybe lld works; I
didn't try). If you link with binutils ld, the program will generate
broken profile information. Apparently, the linked binary is missing
the