Displaying 4 results from an estimated 4 matches for "computesymbolsizes".
2015 Jul 15
2
[LLVMdev] SymbolRef and getSize
Hi everyone,
I’m currently playing with the clang driver and I encounter a strange bug.
It occurs when I used the getSize function from the SymbolRef class.
On iOS, the number returned is not always correct (some function have the right size).
Sadly,
This is my code (at the end of the main function into driver.cpp) :
####
ErrorOr<OwningBinary<Binary>> BinaryOrErr =
2018 Mar 26
0
Interest in integrating a linux perf JITEventListener?
...j = *DebugObjOwner.getBinary();
> +
> + // Get the address of the object image for use as a unique identifier
> + DWARFContextInMemory Context(DebugObj);
> +
> + // Use symbol info to iterate functions in the object.
> + for (const std::pair<SymbolRef, uint64_t> &P : computeSymbolSizes(DebugObj)) {
> + SymbolRef Sym = P.first;
> + std::vector<LLVMPerfJitDebugEntry> LineInfo;
> + std::string SourceFileName;
> +
> + Expected<SymbolRef::Type> SymTypeOrErr = Sym.getType();
> + if (!SymTypeOrErr) {
> + // TODO: Actually report error...
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