Displaying 5 results from an estimated 5 matches for "__llvm_profile_data".
2017 Oct 25
4
Profiling data structure
...een able to find a lot of documentation
about how this data is stored inside of the different sections, but
with the code in compiler_rt/libs/profile I've been able to craft
something that seems to do something sensible.
I have however a couple of questions:
- The "Values" field in __llvm_profile_data always seems to be NULL.
Is this expected? What/why could cause this?
- The fields in the NumValueSites array inside of __llvm_profile_data
also seem to always be 0.
- Since what I'm coding is a decoupled replacement for the profiling
runtime inside of compiler_rt, is there anyway...
2019 May 16
2
How data is laid out in default.profraw when doing profiling?
...t profraw manually but don't know how data is laid out in `default profraw` file.
We found a struct ProfDataIOVec in InstrProfilingWriter.c in compiler-rt and followed this layout.
```
ProfDataIOVec IOVec[] = {
{&Header, sizeof(__llvm_profile_header), 1},
{DataBegin, sizeof(__llvm_profile_data), DataSize},
{CountersBegin, sizeof(uint64_t), CountersSize},
{SkipNameDataWrite ? NULL : NamesBegin, sizeof(uint8_t), NamesSize},
{Zeroes, sizeof(uint8_t), Padding}};
```
This helped us successfully passed some small cases(not know for sure whether the coverage result is true,...
2017 Oct 26
2
Profiling data structure
...a is stored inside of the different sections, but
> > with the code in compiler_rt/libs/profile I've been able to craft
> > something that seems to do something sensible.
> >
> > I have however a couple of questions:
> >
> > - The "Values" field in __llvm_profile_data always seems to be NULL.
> > Is this expected? What/why could cause this?
> >
>
> This is for value profiling. For now there are only two kinds: indirect
> call targets and memcpy/memset size. If the function body does not have any
> value sites, the field will be null....
2015 May 21
5
[LLVMdev] IC profiling infrastructure
....
- Please use clang-format on your changes. Several of the patches have
unusual or non-llvm-style whitespace/wrapping/etc.
Finally, the LLVM patch is quite large. We can probably make it a bit
easier to stage and review by splitting out a couple of things and doing
them first:
1. Changing the __llvm_profile_data variables so they're no longer
const.
2. Adding the InstrProfRecord type and updating the unittests. Also,
this type should just go in the InstrProf.h header, no need for its
own.
3. Arguably, we could update the raw format and implement the
RawInstrProfReader changes (but ignorin...
2015 May 13
2
[LLVMdev] IC profiling infrastructure
> Xinliang David Li <davidxl at google.com> writes:
>>> From: <betulb at codeaurora.org>
>>> Date: Tue, Apr 7, 2015 at 12:44 PM
>>> Subject: [LLVMdev] IC profiling infrastructure
>>> To: llvmdev at cs.uiuc.edu
>>>
>>>
>>>
>>> Hi All,
>>>
>>> We had sent out an RFC in October on indirect call