Lines Matching refs:Clang

17 When Clang compiles C++ code for Windows, it attempts to be compatible with
20 First, Clang attempts to be ABI-compatible, meaning that Clang-compiled code
22 ABIs are particularly large and complicated, and Clang's support for MSVC's C++
27 Second, Clang implements many MSVC language extensions, such as
31 Third, MSVC accepts some C++ code that Clang will typically diagnose as
33 Clang attempts to recover and continue compiling the user's program.  Most
68   base class`_.  Clang does not yet support this.
75 * Debug info: :partial:`Minimal`.  Clang emits both CodeView line tables
79   enabling stack traces in all modern Windows debuggers.  Clang does not emit
105 * Lambdas: :good:`Mostly complete`.  Clang is compatible with Microsoft's
113 MSVC allows many invalid constructs in class templates that Clang has
116 (WRL), some template rules have been relaxed or extended in Clang on Windows.
120 time.  By default on Windows, Clang attempts to follow suit.  This behavior is
121 controlled by the ``-fdelayed-template-parsing`` flag.  While Clang delays
127 platforms, this has been a `frequently asked question`_ for Clang users.  A
129 parameter.  Clang cannot see any of the names inside dependent bases while it
131 ``typename`` keyword to assist the parser.  On Windows, Clang attempts to
134 following program, Clang will recover as if the user had written the
149 After recovery, Clang warns the user that this code is non-standard and issues
152 As of this writing, Clang is able to compile a simple ATL hello world