[llvm-dev] Not able to use PGO with LLVM+Clang built from source
Chris Bieneman via llvm-dev
llvm-dev at lists.llvm.org
Tue Jul 12 10:41:28 PDT 2016
Ah. I misunderstood. For that case all you need is to build Compiler-RT with your clang.
-Chris
> On Jul 12, 2016, at 11:10 AM, vivek pandya <vivekvpandya at gmail.com> wrote:
>
>
>
>> On Tue, Jul 12, 2016 at 9:07 PM, Chris Bieneman <cbieneman at apple.com> wrote:
>> Vivek, in case you haven't seen it, we do have full support for multi-stage PGO builds in CMake. The documentation is here:
>>
>> http://llvm.org/docs/AdvancedBuilds.html#multi-stage-pgo
>>
>> Your checkout will need to include LLVM, Clang, and Compiler-RT, and it will generate targets to run the full PGO generation. I find that using this is way easier than doing it manually.
>>
> Thanks Chris for pointing this but after reading this it seems to optimize llvm/clang it self , how ever I need to use profile information in a Machine Function pass to help interprocedural register allocation and then use it to optimize other softwares. I have not look into PGO.cmake.
>
> -Vivek
>
>> -Chris
>>
>>> On Jul 12, 2016, at 4:40 AM, vivek pandya via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>>
>>> Hello,
>>>
>>> When I try to use -fprofile-instr-generate with clang (which is built from source) I am getting following error :
>>>
>>> ld: file not found: /Users/Mr.Pandya/My_Stuff/Active/llvm/build/bin/../lib/clang/3.9.0/lib/darwin/libclang_rt.profile_osx.a
>>> clang-3.9: error: linker command failed with exit code 1 (use -v to see invocation)
>>>
>>> I am not building compiler RT with LLVM.
>>>
>>> Am I missing any thing while building llvm/clang ?
>>>
>>> Sincerely,
>>> Vivek
>>> _______________________________________________
>>> 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/20160712/5f0173c3/attachment.html>
More information about the llvm-dev
mailing list