From 79b16276cb0f01f2e7ceb72b32c6136c4997c4b8 Mon Sep 17 00:00:00 2001 From: Chandler Carruth Date: Fri, 23 Dec 2016 23:33:32 +0000 Subject: [PATCH] [PM] Clean up test case and comments a bit. NFC. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@290456 91177308-0d34-0410-b5e6-96231b3b80d8 --- test/Transforms/Inline/always-inline.ll | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/test/Transforms/Inline/always-inline.ll b/test/Transforms/Inline/always-inline.ll index 637fe63e1a7..f0d75c43602 100644 --- a/test/Transforms/Inline/always-inline.ll +++ b/test/Transforms/Inline/always-inline.ll @@ -5,8 +5,11 @@ ; RUN: opt < %s -inline-threshold=-20000000 -always-inline -S | FileCheck %s --check-prefix=CHECK --check-prefix=CHECK-CALL ; ; The new pass manager doesn't re-use any threshold based infrastructure for -; the always inliner, but test that we get the correct result. -; RUN: opt < %s -passes=always-inline -S | FileCheck %s +; the always inliner, but test that we get the correct result. The new PM +; always inliner also doesn't support inlining call-site alwaysinline +; annotations. It isn't clear that this is a reasonable use case for +; 'alwaysinline'. +; RUN: opt < %s -passes=always-inline -S | FileCheck %s --check-prefix=CHECK define i32 @inner1() alwaysinline { ret i32 1