Displaying 5 results from an estimated 5 matches for "__llvm_profiling_metadata".
2017 Jul 01
7
[RFC] Placing profile name data, and coverage data, outside of object files
...e original module, and there are no changes from the current
process. I.e with this proposal we preserve backwards compatibility.
4. Once the metadata module is written, the name/coverage data are entirely
stripped out of the original module. They are replaced by a path to the
metadata module:
@__llvm_profiling_metadata = "<metadata-dir>/<module-hash>.bc",
section "__llvm_prf_link"
This allows incremental builds to work properly, which is an important use case
for code coverage users. When an object is rebuilt, it gets a fresh link to a
fresh profilin...
2017 Jul 01
4
[RFC] Placing profile name data, and coverage data, outside of object files
...d system / overall
system integration right, so it will be worth it in the long run.
-- Sean Silva
>
> 4. Once the metadata module is written, the name/coverage data are entirely
> stripped out of the original module. They are replaced by a path to the
> metadata module:
>
> @__llvm_profiling_metadata = "<metadata-dir>/<module-hash>.bc",
> section "__llvm_prf_link"
>
> This allows incremental builds to work properly, which is an important use
> case
> for code coverage users. When an object is rebuilt, it gets a fresh...
2017 Jul 01
3
[RFC] Placing profile name data, and coverage data, outside of object files
...will be worth it in the long run.
>
> -- Sean Silva
>
>
>>
>> 4. Once the metadata module is written, the name/coverage data are
>> entirely
>> stripped out of the original module. They are replaced by a path to the
>> metadata module:
>>
>> @__llvm_profiling_metadata = "<metadata-dir>/<module-hash>.bc",
>> section "__llvm_prf_link"
>>
>> This allows incremental builds to work properly, which is an important
>> use case
>> for code coverage users. When an object is rebui...
2017 Jul 01
0
[RFC] Placing profile name data, and coverage data, outside of object files
...preserve backwards compatibility.
>
>
Or simply emit the raw file as coverage notes files (gcno).
> 4. Once the metadata module is written, the name/coverage data are entirely
> stripped out of the original module. They are replaced by a path to the
> metadata module:
>
> @__llvm_profiling_metadata = "<metadata-dir>/<module-hash>.bc",
> section "__llvm_prf_link"
>
> This allows incremental builds to work properly, which is an important use
> case
> for code coverage users. When an object is rebuilt, it gets a fresh...
2017 Jul 01
0
[RFC] Placing profile name data, and coverage data, outside of object files
...>> -- Sean Silva
>>
>>
>>>
>>> 4. Once the metadata module is written, the name/coverage data are
>>> entirely
>>> stripped out of the original module. They are replaced by a path to the
>>> metadata module:
>>>
>>> @__llvm_profiling_metadata = "<metadata-dir>/<module-hash>.bc",
>>> section "__llvm_prf_link"
>>>
>>> This allows incremental builds to work properly, which is an important
>>> use case
>>> for code coverage users. Whe...