Lines Matching full:clang
22 <p>Clang strives to both conform to current language standards (C99,
25 compiler with Clang. However, Clang is more strict than other
28 portability issues with Clang to help you understand and fix the
29 problem in your code when Clang emits an error message.</p>
86 <p>By default, Clang builds C code according to the C99 standard,
131 Some compilers ignore it completely. Clang treats it as a mild
139 <code>-std=gnu89</code> to the set of Clang options. This option is
156 however they want. Since Clang supports an excellent set of <a
158 the Clang headers implement these interfaces in terms of the native vector
165 the Intel compiler, the Microsoft compiler, or Clang. If you get build errors
188 different type. Clang produces an error on similar code, e.g.,</p>
208 <p>Clang disallows jumps into the scope of a <tt>__block</tt>
231 the stack is fresh, i.e. still zeroed.) Therefore, Clang rejects this
274 <p>Clang does not zero initialize local block variables, and programs which rely
275 on such behavior will most likely break when built with Clang.</p>
282 <p>In general, Clang is highly compatible with the GCC inline assembly
301 <p>Both clang and GAS accept the first instruction: because the first
306 the assembler randomly picks a 32-bit add). Because it is ambiguous, Clang
318 this makes your code more clear and is compatible with both GCC and Clang.</p>
329 can, among other things, be cast to a different type. Clang treats
350 (or removed). For this reason, Clang rejects the application of the
376 <tt>id</tt>, <tt>SEL</tt>, and <tt>Class</tt> respectively. Clang treats the
397 declaration. Clang does not allow variable declarations to appear
404 int a; // not allowed in clang
405 int b = 1; // not allowed in clang
420 time. This extension is not permitted in standard C++. However, Clang
433 <p>If your code uses variable length arrays in a manner that Clang doesn't support, there are several ways to fix your code:
466 <p>Clang complains:
527 <p>Again, Clang complains:</p>
586 Clang correctly rejects it with the following errors
613 <p>The fix, as Clang tells you, is to tell the compiler that we want a
659 write <tt>opts.ForceReads</tt> in the code above. In Clang, we feel
706 ill-formed. Clang tries to do as much checking as possible at
710 philosophy is that Clang sometimes fails to process files because they
761 <p>Clang diagnoses this error (where the parameter name has been redeclared). To fix this problem, rename one of the parameters.</p>
775 implementations of C++11 (including Clang before 3.0, GCC before 4.7,
807 rejected by Clang. For example, given this code:</p>
819 <p>Clang produces the following error:</p>
846 Clang permits <code>class</code> to be used as part of a method
