Displaying 5 results from an estimated 5 matches for "__llvm_prf_link".
2017 Jul 01
7
[RFC] Placing profile name data, and coverage data, outside of object files
...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 profiling metadata file. Although stale files can accumulate in the
metadata directory, the stale files cannot ever be used.
In...
2017 Jul 01
4
[RFC] Placing profile name data, and coverage data, outside of object files
...dule 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 profiling metadata file. Although stale files can accumulate in the
> metadata directory, the st...
2017 Jul 01
3
[RFC] Placing profile name data, and coverage data, outside of object files
...erage 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 profiling metadata file. Although stale files can accumulate in the
>>...
2017 Jul 01
0
[RFC] Placing profile name data, and coverage data, outside of object files
...dule 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 profiling metadata file. Although stale files can accumulate in the
> metadata directory, the st...
2017 Jul 01
0
[RFC] Placing profile name data, and coverage data, outside of object files
...gt; 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 profiling metadata file. Although stale files can a...