File: cb_error.hlsl

package info (click to toggle)
swiftlang 6.1.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,791,604 kB
  • sloc: cpp: 9,901,740; ansic: 2,201,431; asm: 1,091,827; python: 308,252; objc: 82,166; f90: 80,126; lisp: 38,358; pascal: 25,559; sh: 20,429; ml: 5,058; perl: 4,745; makefile: 4,484; awk: 3,535; javascript: 3,018; xml: 918; fortran: 664; cs: 573; ruby: 396
file content (49 lines) | stat: -rw-r--r-- 1,084 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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
// RUN: %clang_cc1 -triple dxil-pc-shadermodel6.3-library -x hlsl -o - -fsyntax-only %s -verify

// expected-note@+1 {{declared here}}
cbuffer a {
  int x;
};

int foo() {
  // expected-error@+1 {{'a' does not refer to a value}}
  return sizeof(a);
}

// expected-error@+1 {{expected unqualified-id}}
template <typename Ty> cbuffer a { Ty f; };

// For back-compat reason, it is OK for multiple cbuffer/tbuffer use same name in hlsl.
// And these cbuffer name only used for reflection, cannot be removed.
cbuffer A {
  float A;
}

cbuffer A {
  float b;
}

tbuffer A {
  float a;
}

float bar() {
  // cbuffer/tbuffer name will not conflict with other variables.
  return A;
}

cbuffer a {
  // expected-error@+2 {{unknown type name 'oh'}}
  // expected-error@+1 {{expected ';' after top level declarator}}
  oh no!
  // expected-warning@+1 {{missing terminating ' character}}
  this isn't even valid HLSL code
  despite seeming totally reasonable
  once you understand that HLSL
  is so flaming weird.
}

tbuffer B {
  // expected-error@+1 {{unknown type name 'flaot'}}
  flaot f;
}