brintos

brintos / llvm-project-archived public Read only

0
0
Text · 1.1 KiB · cd56e67 Raw
35 lines · plain
1# RUN: yaml2obj %S/Inputs/inlined-file0-line0-col0.yaml -o %t2# RUN: %lldb %t -s %s -o exit | FileCheck %s3 4#  1 void abort(void);5#  2 int g1 = 4, g2 = 6;6#  37#  4 inline __attribute__((always_inline)) void bar(int q) {8#  5   if (q > 5)9#  6     abort();10#  7 }11#  812#  9 inline __attribute__((always_inline)) void foo(int q) {13# 10   bar(q);14# 11 }15# 1216# 13 int main() {17# 14   foo(g1);18# 15   foo(g2);19# 16   return 0;20# 17 }21 22# The input object file contains a single abort invocation for the two inlined23# instances of foo() in main() at line 0. As the file, line and column numbers24# are all 0, file and line number information would be missing for foo and main25# in the lookup information.26#27# A line number 0 is not printed for main in this case, but the same holds28# for a non-inlined location with line number 0.29 30# CHECK: Summary: inlined-file0-line0-col0.test.tmp`main + 30 [inlined] bar + 4 at inlined-file0-line0-col0.c:6:531# CHECK-NEXT:     inlined-file0-line0-col0.test.tmp`main + 26 [inlined] foo at inlined-file0-line0-col0.c:10:332# CHECK-NEXT:     inlined-file0-line0-col0.test.tmp`main + 26 at inlined-file0-line0-col0.c33 34image lookup -a 0x1e35