Paul Hancock via llvm-dev
2016-Aug-17 06:55 UTC
[llvm-dev] LLVM IR allocation optimisation
I couldn't find any straight answers about this, but is modern LLVM (3.7.1 in my case) "smart enough" to automatically handle "temporary variable" allocations as efficiently as possible without me needing to put them all at the very start of the function? or is building IR with allocations as they are in the original code (ie; scattered throughout the function's code) still "problematic" when it comes to performance? - Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160817/9e33f359/attachment.html>
Looks like you should refer to: http://llvm.org/docs/Frontend/PerformanceTips.html#use-of-allocas <http://llvm.org/docs/Frontend/PerformanceTips.html#use-of-allocas> — Mehdi> On Aug 16, 2016, at 11:55 PM, Paul Hancock via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I couldn't find any straight answers about this, but is modern LLVM (3.7.1 in my case) "smart enough" to automatically handle "temporary variable" allocations as efficiently as possible without me needing to put them all at the very start of the function? or is building IR with allocations as they are in the original code (ie; scattered throughout the function's code) still "problematic" when it comes to performance? > > - Paul > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev <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/20160817/d21b741f/attachment.html>