maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/test/CodeGenObjC/debug-info-self.m

20 lines
813 B
Mathematica
Raw Normal View History

Update tests in preparation for using the MS ABI for Win32 targets In preparation for making the Win32 triple imply MS ABI mode, make all tests pass in this mode, or make them use the Itanium mode explicitly. Differential Revision: http://llvm-reviews.chandlerc.com/D2401 llvm-svn: 199130
2014-01-14 03:48:13 +08:00
// RUN: %clang_cc1 -emit-llvm -cxx-abi itanium -g %s -o - | FileCheck %s
Attach aritifical attribute with implicit parameters. Radar 8493141. llvm-svn: 115104
2010-09-30 07:09:21 +08:00
// self and _cmd are marked as DW_AT_artificial.
// myarg is not marked as DW_AT_artificial.
@interface MyClass {
}
- (id)init:(int) myarg;
@end
@implementation MyClass
- (id) init:(int) myarg
{
return self;
}
@end
Generalize DebugInfo tests by avoiding explicit metadata numbers This addresses several (not all) debug info tests that use explicit metadata numbers. Wherever the same number appeared more than once in a test I used a named match to ensure the same number appeared in all those cases (this may still be overly constraining test cases as they may not have actually cared about that relationship). For one-off numbers I just replaced them with an unnamed regex. This may underconstrain poorly written test cases that were interested in checking that certain metadata nodes were related but didn't actually match on all the related nodes numbers. llvm-svn: 174247
2013-02-02 08:34:26 +08:00
DebugInfo: Do not include line/file info for artificial parameters & parameters of artificial functions llvm-svn: 188651
2013-08-19 11:37:48 +08:00
// CHECK: metadata !{i32 {{.*}}, metadata ![[CTOR:.*]], metadata !"self", null, i32 16777216, metadata !{{.*}}, i32 1088, i32 0} ; [ DW_TAG_arg_variable ] [self] [line 0]
// CHECK: metadata !{i32 {{.*}}, metadata ![[CTOR]], metadata !"_cmd", null, i32 33554432, metadata !{{.*}}, i32 64, i32 0} ; [ DW_TAG_arg_variable ] [_cmd] [line 0]
Generalize DebugInfo tests by avoiding explicit metadata numbers This addresses several (not all) debug info tests that use explicit metadata numbers. Wherever the same number appeared more than once in a test I used a named match to ensure the same number appeared in all those cases (this may still be overly constraining test cases as they may not have actually cared about that relationship). For one-off numbers I just replaced them with an unnamed regex. This may underconstrain poorly written test cases that were interested in checking that certain metadata nodes were related but didn't actually match on all the related nodes numbers. llvm-svn: 174247
2013-02-02 08:34:26 +08:00
// CHECK: metadata !{i32 {{.*}}, metadata ![[CTOR]], metadata !"myarg", metadata !{{.*}}, i32 50331659, metadata !{{.*}}, i32 0, i32 0} ; [ DW_TAG_arg_variable ] [myarg] [line 11]