[llvm-dev] profile the llvm JITed code

[Lang Hames via llvm-dev]

Hi Mark,

Thanks very much for digging in to this. I'm glad to hear that it's fixed
in newer versions of LLVM.

Cheers,
Lang.


On Fri, Sep 25, 2015 at 8:57 PM, Mark Dewing via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Hi,
>   The issue is with a change in OProfile.  It used to be run with
> 'opcontrol', but now is run using 'operf'.
> There is a check in lib/ExecutionEngine/OProfileJIT/OProfileWrapper.cpp to
> see if OProfile is running.  Older versions check only for 'oprofiled'.
> Newer versions also check for 'operf'.
> One fix is the change the check to match the newer code.
> Alternately, you could make a fake program called 'oprofiled' (it just
> needs to sleep), and make sure it is running when doing profiling.
>
> Mark
>
>
>> Hi llvm,
>> It is the second time I post this kind of message.
>>
>> My llvm version is 3.3, can anyone tell me how to profile the JITed code
>> using OProfile?
>
>
> (rest of message removed)
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150926/1ed9b355/attachment.html>