<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">There have been extensive discussions about this on about 8 month ago on the mailing list. You’ll also find some comments in the code. We first have to improve points-to analysis before we think about revisiting inlining functions with indirect branches.<div class=""><br class=""></div><div class="">Always-inline just means inline when the compiler can determine that it is safe to so.</div><div class=""><br class=""></div><div class="">-Gerolf<br class=""><div class=""><br class=""></div><div class=""><div class=""><div class="">]. <br class=""><div><blockquote type="cite" class=""><div class="">On Jan 29, 2015, at 11:27 AM, Xin Tong <<a href="mailto:trent.tong@gmail.com" class="">trent.tong@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:courier new,monospace">I see that we do not inline a function marked as "always-inline" if it contains indirect branches ? what are the reasons behind this criterion ?</div><div class="gmail_default" style="font-family:courier new,monospace"><br class=""></div><div class="gmail_default" style="font-family:courier new,monospace">Thanks</div><div class="gmail_default" style="font-family:courier new,monospace">Trent</div></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:LLVMdev@cs.uiuc.edu" class="">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" class="">http://llvm.cs.uiuc.edu</a><br class=""><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" class="">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br class=""></div></blockquote></div><br class=""></div></div></div></div></body></html>