Displaying 3 results from an estimated 3 matches for "code_addr".
Did you mean:
ucode_addr
2018 Mar 26
0
Interest in integrating a linux perf JITEventListener?
...;
> + rec.Prefix.TotalSize += line.FileName.size() + 1;
> + }
> +
> + Dumpstream->write(reinterpret_cast<const char *>(&rec), sizeof(rec));
> +
> + // The debug_entry describes the source line information. It is defined as follows in order:
> + // * uint64_t code_addr: address of function for which the debug information is generated
> + // * uint32_t line : source file line number (starting at 1)
> + // * uint32_t discrim : column discriminator, 0 is default
> + // * char name[n] : source file name in ASCII, including null termination
>...
2016 Dec 29
1
Interest in integrating a linux perf JITEventListener?
Having something like this available in tree would definitely be
useful. For simplicity, why don't we start with support for the second
style? This is the long term useful one and would be a good starting
point for getting the code in tree. Can you give a pointer to the patch
so that I can assess the rough complexity? If it's simple enough, I'd
be happy to help get it reviewed
2017 Feb 02
0
Interest in integrating a linux perf JITEventListener?
Hi,
On 2016-12-29 13:17:50 -0800, Philip Reames wrote:
> Having something like this available in tree would definitely be
> useful.
Cool.
> For simplicity, why don't we start with support for the second style? This
> is the long term useful one and would be a good starting point for getting
> the code in tree.
Works for me.
> Can you give a pointer to the patch so that