maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/Frontend/ir-support-codegen.ll

16 lines
464 B
LLVM
Raw Normal View History

clang/test: REQUIRES: s/x86-64-registered-target/x86-registered-target/ llvm-svn: 196350
2013-12-04 11:41:33 +08:00
; REQUIRES: x86-registered-target
Override the datalayout in a module with -triple. This matches llc's behavior. Before this patch clang would create a TargetInfo base on -triple but a llvm CodeGen based on the triple in the module. llvm-svn: 197837
2013-12-21 06:01:25 +08:00
; RUN: %clang_cc1 -triple x86_64-apple-darwin10 -S -o - %s | FileCheck %s
; RUN: %clang_cc1 -triple x86_64-pc-linux -S -o %t %s 2>&1 | \
; RUN: FileCheck --check-prefix=WARN %s
; WARN: warning: overriding the module target triple with x86_64-pc-linux
; RUN: FileCheck --check-prefix=LINUX %s < %t
Frontend: Add CodeGenAction support for handling LLVM IR. - This magically enables using 'clang -cc1' as a replacement for most of 'llvm-as', 'llvm-dis', 'llc' and 'opt' functionality. For example, 'llvm-as' is: $ clang -cc1 -emit-llvm-bc FOO.ll -o FOO.bc and 'llvm-dis' is: $ clang -cc1 -emit-llvm FOO.bc -o - and 'opt' is, e.g.: $ clang -cc1 -emit-llvm -O3 -o FOO.opt.ll FOO.ll and 'llc' is, e.g.: $ clang -cc1 -S -o - FOO.ll The nice thing about using the backend tools this way is that they are guaranteed to exactly match how the compiler generates code (for example, setting the same backend options). llvm-svn: 105583
2010-06-08 07:27:59 +08:00
target triple = "x86_64-apple-darwin10"
; CHECK: .globl _f0
Override the datalayout in a module with -triple. This matches llc's behavior. Before this patch clang would create a TargetInfo base on -triple but a llvm CodeGen based on the triple in the module. llvm-svn: 197837
2013-12-21 06:01:25 +08:00
; LINUX: .globl f0
Frontend: Add CodeGenAction support for handling LLVM IR. - This magically enables using 'clang -cc1' as a replacement for most of 'llvm-as', 'llvm-dis', 'llc' and 'opt' functionality. For example, 'llvm-as' is: $ clang -cc1 -emit-llvm-bc FOO.ll -o FOO.bc and 'llvm-dis' is: $ clang -cc1 -emit-llvm FOO.bc -o - and 'opt' is, e.g.: $ clang -cc1 -emit-llvm -O3 -o FOO.opt.ll FOO.ll and 'llc' is, e.g.: $ clang -cc1 -S -o - FOO.ll The nice thing about using the backend tools this way is that they are guaranteed to exactly match how the compiler generates code (for example, setting the same backend options). llvm-svn: 105583
2010-06-08 07:27:59 +08:00
define i32 @f0() nounwind ssp {
ret i32 0
}