diff options
author | Kit Barton <kbarton@ca.ibm.com> | 2018-08-28 01:18:29 +0000 |
---|---|---|
committer | Kit Barton <kbarton@ca.ibm.com> | 2018-08-28 01:18:29 +0000 |
commit | 7c80f98b69a6a9ad027a3f4bfda073958141d977 (patch) | |
tree | b00608f900c4cc4e9a8571ed3092baaedb5c19c9 /llvm/test/CodeGen/PowerPC/debuginfo-stackarg.ll | |
parent | 7d30653259ea08b06945239c2124d13a7401ee53 (diff) | |
download | bcm5719-llvm-7c80f98b69a6a9ad027a3f4bfda073958141d977.tar.gz bcm5719-llvm-7c80f98b69a6a9ad027a3f4bfda073958141d977.zip |
[PPC] Remove Darwin support from POWER backend.
This patch issues an error message if Darwin ABI is attempted with the PPC
backend. It also cleans up existing test cases, either converting the test to
use an alternative triple or removing the test if the coverage is no longer
needed.
Updated Tests
-------------
The majority of test cases were updated to use a different triple that does not
include the Darwin ABI. Many tests were also updated to use FileCheck, in place
of grep.
Deleted Tests
-------------
llvm/test/tools/dsymutil/PowerPC/sibling.test was originally added to test
specific functionality of dsymutil using an object file created with an old
version of llvm-gcc for a Powerbook G4. After a discussion with @JDevlieghere he
suggested removing the test.
llvm/test/CodeGen/PowerPC/combine_loads_from_build_pair.ll was converted from a
PPC test to a SystemZ test, as the behavior is also reproducible there.
All other tests that were deleted were specific to the darwin/ppc ABI and no
longer necessary.
Phabricator Review: https://reviews.llvm.org/D50988
llvm-svn: 340795
Diffstat (limited to 'llvm/test/CodeGen/PowerPC/debuginfo-stackarg.ll')
-rw-r--r-- | llvm/test/CodeGen/PowerPC/debuginfo-stackarg.ll | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/llvm/test/CodeGen/PowerPC/debuginfo-stackarg.ll b/llvm/test/CodeGen/PowerPC/debuginfo-stackarg.ll index 7eb56d80123..3830589b4cb 100644 --- a/llvm/test/CodeGen/PowerPC/debuginfo-stackarg.ll +++ b/llvm/test/CodeGen/PowerPC/debuginfo-stackarg.ll @@ -12,7 +12,8 @@ ; ModuleID = 'debuginfo-stackarg.c' source_filename = "debuginfo-stackarg.c" target datalayout = "E-m:o-p:32:32-f64:32:64-n32" -target triple = "powerpc-apple-macosx10.5.0" +;;;target triple = "powerpc-apple-macosx10.5.0" +target triple = "powerpc-unknown-linux-gnu" ; Function Attrs: nounwind readnone ssp uwtable define i64 @foo(i64 %bar1, i64 %bar2, i64 %bar3, i64 %bar4, i64 %bar5) local_unnamed_addr #0 !dbg !8 { @@ -24,8 +25,8 @@ define i64 @foo(i64 %bar1, i64 %bar2, i64 %bar3, i64 %bar4, i64 %bar5) local_unn ; ; Now check that we got two entries on the fixed stack with "expected" offsets. ; CHECK-LABEL: fixedStack: -; CHECK: id: 0, type: default, offset: 60, size: 4 -; CHECK: id: 1, type: default, offset: 56, size: 4 +; CHECK: id: 0, type: default, offset: 12, size: 4 +; CHECK: id: 1, type: default, offset: 8, size: 4 ; CHECK-NOT: id: 2 ; CHECK-LABEL: stack: ; @@ -33,7 +34,7 @@ define i64 @foo(i64 %bar1, i64 %bar2, i64 %bar3, i64 %bar4, i64 %bar5) local_unn ; We expect to find a DBG_VALUE refering to the metadata id for bar5, using the lowest ; of the two fixed stack offsets found earlier. ; CHECK-LABEL: body: -; CHECK: DBG_VALUE debug-use $r1, 0, !17, !DIExpression(DW_OP_plus_uconst, 56) +; CHECK: DBG_VALUE debug-use $r1, 0, !17, !DIExpression(DW_OP_plus_uconst, 8) entry: tail call void @llvm.dbg.value(metadata i64 %bar1, metadata !13, metadata !DIExpression()), !dbg !18 tail call void @llvm.dbg.value(metadata i64 %bar2, metadata !14, metadata !DIExpression()), !dbg !19 |