mtrofin added a comment. In D88114#2288732 <https://reviews.llvm.org/D88114#2288732>, @steven_wu wrote:
> I am not sure what exactly is expected here. What is your definition for > pre-optimized bitcode and how your test case ensures that? Can you explain a > bit more for context? Pre-optimized meaning before the llvm optimization pipeline is called. That's the current implementation, and the test explicitly checks that the inlining of bar into foo doesn't happen. I could add an "alwaysinline" to bar, to further stress that. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D88114/new/ https://reviews.llvm.org/D88114 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
