File: debug-info-block-out-return.c

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,998,520 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (25 lines) | stat: -rw-r--r-- 1,108 bytes parent folder | download | duplicates (13)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
// RUN: %clang_cc1 -triple x86_64-apple-darwin10 -debug-info-kind=limited -fblocks -emit-llvm -o - %s | FileCheck %s

// Check that arg numbering is not affected by LLVM IR argument numbering -
// since the latter is affected by return-by-out-parameter ABI requirements

// 1 for the argument number (1 indexed), 2 for the line number
// 16777218 == 1 << 24 | 2
// 33554434 == 2 << 24 | 2
// This explains the two magic numbers below, testing that these two arguments
// are numbered correctly. If they are not numbered correctly they may appear
// out of order or not at all (the latter would occur if they were both assigned
// the same argument number by mistake).

// CHECK: !DILocalVariable(name: ".block_descriptor", arg: 1,{{.*}}line: 2,
// CHECK: !DILocalVariable(name: "param", arg: 2,{{.*}}line: 2,

// Line directive so we don't have to worry about how many lines precede the
// test code (as the line number is mangled in with the argument number as shown
// above)
#line 1
typedef struct { int array[12]; } BigStruct_t;
BigStruct_t (^a)(int) = ^(int param) {
    BigStruct_t b;
    return b;
};