Displaying 6 results from an estimated 6 matches for "pr33501".
2017 Jun 27
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
On 6/19/2017 7:29 PM, Vedant Kumar wrote:
>
>>> We can reduce testing time by *not* instrumented basic tools like
>>> count, not, FileCheck etc. I filed: llvm.org/PR33501
>>> <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
>>&...
2017 Jun 19
3
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...IR PGO to AST nodes, we could improve the
> situation. I filed: llvm.org/PR33500 <http://llvm.org/PR33500>.
This would be nice... but I assume it's hard. :)
>
> We can reduce testing time by *not* instrumented basic tools like
> count, not, FileCheck etc. I filed: llvm.org/PR33501
> <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
> LL...
2017 Jun 27
2
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...t;efriedma at codeaurora.org <mailto:efriedma at codeaurora.org>> wrote:
>
> On 6/19/2017 7:29 PM, Vedant Kumar wrote:
>>
>>>> We can reduce testing time by *not* instrumented basic tools
>>>> like count, not, FileCheck etc. I filed: llvm.org/PR33501
>>>> <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...
2017 Jun 27
2
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...:24 PM, Friedman, Eli <efriedma at codeaurora.org>
>> wrote:
>>
>>> On 6/19/2017 7:29 PM, Vedant Kumar wrote:
>>>
>>>
>>> We can reduce testing time by *not* instrumented basic tools like count,
>>> not, FileCheck etc. I filed: 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 alte...
2017 Jun 27
4
My experience using -DLLVM_BUILD_INSTRUMENTED_COVERAGE to generate coverage
...n, Eli <efriedma at codeaurora.org <mailto:efriedma at codeaurora.org>> wrote:
>>> On 6/19/2017 7:29 PM, Vedant Kumar wrote:
>>>>
>>>>>> We can reduce testing time by *not* instrumented basic tools like count, not, FileCheck etc. I filed: llvm.org/PR33501 <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 decre...
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