[llvm-dev] Finding which optimization passes have failed

Francis Visoiu Mistrih via llvm-dev llvm-dev at lists.llvm.org
Mon Nov 19 11:10:43 PST 2018


Hello,

You might be looking for optimization remarks.

You should take a look at the -fsave-optimization-record and -Rpass* flags.

Cheers,

-- 
Francis

> On 19 Nov 2018, at 04:14, Bekket McClane via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> 
> 
> 
>> On Nov 17, 2018, at 8:20 AM, Pradeep Kumar via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> 
>> Dear LLVM community,
>>   How to find out which optimization passes have been performed and which passes have failed?
> 
> First please define “failed”. 
> If you mean “crash”, there will be a stack dump anyway.
> If you mean failed to optimize the code(into better code for example), the opt option “-print-after-all” might help you, it would print the result IR after each optimization passes.
> 
> Regarding which optimization do clang run, clang option “-mllvm -debug-pass=Arguments” might be the thing you’re looking for
> 
> Bests,
> Bekket
>> 
>> Regards,
>> Pradeep Kumar
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 
> _______________________________________________
> 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/20181119/038ac755/attachment.html>


More information about the llvm-dev mailing list