Home
last modified time | relevance | path

Searched full:compilers (Results 1 – 25 of 2519) sorted by relevance

12345678910>>...101

/external/google-fruit/extras/benchmark/suites/
Dfruit_full.yml21 compilers: &compilers
35 compiler: *compilers
52 compiler: *compilers
63 compiler: *compilers
80 compiler: *compilers
92 compiler: *compilers
Ddebug.yml24 compilers: &compilers
36 compiler: *compilers
66 compiler: *compilers
80 compiler: *compilers
161 compiler: *compilers
173 compiler: *compilers
Dfruit_mostly_full.yml21 compilers: &compilers
32 compiler: *compilers
49 compiler: *compilers
60 compiler: *compilers
Dboost_di.yml21 compilers: &compilers
38 compiler: *compilers
52 compiler: *compilers
Dfruit_quick.yml21 compilers: &compilers
32 compiler: *compilers
50 compiler: *compilers
Dsimple_di_mostly_full.yml24 compilers: &compilers
54 compiler: *compilers
68 compiler: *compilers
Dsimple_di_full.yml24 compilers: &compilers
55 compiler: *compilers
68 compiler: *compilers
Dfruit_single.yml23 compilers: &compilers
32 compiler: *compilers
/external/icu/icu4c/source/
DrunConfigureICU39 AIX Use the IBM XL xlclang/xlclang compilers on AIX
40 AIX/GCC Use the GNU gcc/g++ compilers on AIX
41 Cygwin Use the GNU gcc/g++ compilers on Cygwin
45 FreeBSD Use the clang/clang++ or GNU gcc/g++ compilers on FreeBSD
46 HP-UX/ACC Use the HP ANSI C/Advanced C++ compilers on HP-UX 11
47 IBMi Use the iCC compilers on IBM i, i5/OS, OS/400
48 Linux Use the clang/clang++ or GNU gcc/g++ compilers on Linux
49 Linux/gcc Use the GNU gcc/g++ compilers on Linux
53 MacOSX Use the default compilers on MacOS X (Darwin)
54 MacOSX/GCC Use the GNU gcc/g++ compilers on MacOSX (Darwin)
[all …]
/external/llvm/docs/HistoricalNotes/
D2001-04-16-DynamicCompilation.txt5 compilers, and second, we need a flexible and powerful interface
15 other side, traditional static compilers process everything statically and
25 compilers that support profile guided optimization generate poor code in
36 to when compilers generate quality code for the architecture. Secondly,
37 even when compilers catch up to the new architecture there is often a large
45 independent, static, program optimizations currently in compilers to be
/external/llvm-project/llvm/docs/HistoricalNotes/
D2001-04-16-DynamicCompilation.txt5 compilers, and second, we need a flexible and powerful interface
15 other side, traditional static compilers process everything statically and
25 compilers that support profile guided optimization generate poor code in
36 to when compilers generate quality code for the architecture. Secondly,
37 even when compilers catch up to the new architecture there is often a large
45 independent, static, program optimizations currently in compilers to be
/external/proguard/docs/manual/
Dattributes.html89 just like ordinary classes. Compilers may need this information to find
95 <dd>Specifies the method in which the class was defined. Compilers may need
109 <dd>Specifies the generic signature of the class, field, or method. Compilers
120 <dd>Specifies the exceptions that a method may throw. Compilers may use this
140 fields, and methods. Compilers and annotation processors may use these
146 fields, and methods. Compilers and annotation processors may use these
152 parameters. Compilers and annotation processors may use these
158 parameters. Compilers and annotation processors may use these
164 instructions, etc. Compilers and annotation processors may use these
170 types, instructions, etc. Compilers and annotation processors may use
/external/tensorflow/tensorflow/compiler/mlir/g3doc/
Doverview.md7 and low-level compilers/executors that generate hardware-specific code.
10 compilers. This means it consists of a specification for intermediate
30 compilers and hardware acceleration.
32 The TensorFlow ecosystem contains a number of compilers and optimizers that
/external/llvm-project/lldb/packages/Python/lldbsuite/test/
Ddecorators.py108 # or with arguments (e.g. @expectedFailureWindows(compilers=['gcc'])). When called
139 # or with arguments (e.g. @expectedFailureWindows(compilers=['gcc'])). When called
395 compilers=None, argument
401 compiler=compilers,
406 def expectedFailureDarwin(bugnumber=None, compilers=None, debug_info=None, archs=None): argument
412 compilers,
448 # or with arguments (e.g. @expectedFailureWindows(compilers=['gcc'])). When called
458 def expectedFlakeyOS(oslist, bugnumber=None, compilers=None): argument
461 self.expectedCompiler(compilers))
465 def expectedFlakeyDarwin(bugnumber=None, compilers=None): argument
[all …]
/external/tensorflow/tensorflow/compiler/xla/service/
Dcompiler.cc86 auto* compilers = GetPlatformCompilers(); in GetForPlatform() local
89 auto it = compilers->find(platform->id()); in GetForPlatform()
90 if (it != compilers->end()) { in GetForPlatform()
115 compilers->insert(std::make_pair(platform->id(), it->second())); in GetForPlatform()
116 return compilers->at(platform->id()).get(); in GetForPlatform()
/external/dagger2/javatests/dagger/internal/codegen/
DBUILD37 name = "compilers",
40 "Compilers.java",
59 "Compilers.java",
67 ":compilers",
/external/angle/third_party/vulkan-deps/spirv-tools/src/source/fuzz/fact_manager/
Dfact_manager.cpp145 (void)success; // Keep compilers happy in release mode. in AddFactDataSynonym()
212 (void)success; // Keep compilers happy in release mode. in AddFactBlockIsDead()
224 (void)success; // Keep compilers happy in release mode. in AddFactFunctionIsLivesafe()
245 (void)success; // Keep compilers happy in release mode. in AddFactValueOfPointeeIsIrrelevant()
254 (void)success; // Keep compilers happy in release mode. in AddFactIdIsIrrelevant()
268 (void)success; // Keep compilers happy in release mode. in AddFactIdEquation()
/external/deqp-deps/SPIRV-Tools/source/fuzz/fact_manager/
Dfact_manager.cpp145 (void)success; // Keep compilers happy in release mode. in AddFactDataSynonym()
212 (void)success; // Keep compilers happy in release mode. in AddFactBlockIsDead()
224 (void)success; // Keep compilers happy in release mode. in AddFactFunctionIsLivesafe()
245 (void)success; // Keep compilers happy in release mode. in AddFactValueOfPointeeIsIrrelevant()
254 (void)success; // Keep compilers happy in release mode. in AddFactIdIsIrrelevant()
268 (void)success; // Keep compilers happy in release mode. in AddFactIdEquation()
/external/swiftshader/third_party/SPIRV-Tools/source/fuzz/fact_manager/
Dfact_manager.cpp145 (void)success; // Keep compilers happy in release mode. in AddFactDataSynonym()
212 (void)success; // Keep compilers happy in release mode. in AddFactBlockIsDead()
224 (void)success; // Keep compilers happy in release mode. in AddFactFunctionIsLivesafe()
245 (void)success; // Keep compilers happy in release mode. in AddFactValueOfPointeeIsIrrelevant()
254 (void)success; // Keep compilers happy in release mode. in AddFactIdIsIrrelevant()
268 (void)success; // Keep compilers happy in release mode. in AddFactIdEquation()
/external/skia/site/docs/user/
Dbuild.md15 - [Supported and Preferred Compilers](#compilers)
49 ## <span id="compilers">Supported and Preferred Compilers</span>
51 While Skia should compile with GCC, MSVC, and other compilers, a number of
56 prioritization; there is nothing fundamentally wrong with non-Clang compilers.
61 the features of the c++17 standard. Older compilers that lack C++17 support may
349 Other compilers get generic unoptimized code.
390 `Visual C++ compilers and libraries for ARM64` individual component in the
/external/llvm/include/llvm/Support/
DCompiler.h137 // Some compilers warn about unused functions. When a function is sometimes
183 /// LLVM_ATTRIBUTE_NOINLINE - On compilers where we have a directive to do so,
193 /// LLVM_ATTRIBUTE_ALWAYS_INLINE - On compilers where we have a directive to do
231 /// LLVM_EXTENSION - Support compilers where we have a keyword to suppress
254 /// LLVM_BUILTIN_UNREACHABLE - On compilers which support it, expands
263 /// LLVM_BUILTIN_TRAP - On compilers which support it, expands to an expression
277 /// LLVM_BUILTIN_DEBUGTRAP - On compilers which support it, expands to
288 // Just continue execution when built with compilers that have no
366 /// \brief Expands to __func__ on compilers which support it. Otherwise,
471 // Clang, GCC, and other compatible compilers used __thread prior to C++11 and
/external/llvm-project/clang-tools-extra/docs/clang-tidy/checks/
Dmodernize-use-override.rst10 user that a function was virtual. C++ compilers did not use the presence of
15 compilers to verify that an overridden function correctly overrides a base
18 This can be useful as compilers can generate a compile time error when:
/external/swiftshader/third_party/llvm-subzero/include/llvm/Support/
DCompiler.h139 // Some compilers warn about unused functions. When a function is sometimes
185 /// LLVM_ATTRIBUTE_NOINLINE - On compilers where we have a directive to do so,
195 /// LLVM_ATTRIBUTE_ALWAYS_INLINE - On compilers where we have a directive to do
255 /// LLVM_EXTENSION - Support compilers where we have a keyword to suppress
278 /// LLVM_BUILTIN_UNREACHABLE - On compilers which support it, expands
287 /// LLVM_BUILTIN_TRAP - On compilers which support it, expands to an expression
301 /// LLVM_BUILTIN_DEBUGTRAP - On compilers which support it, expands to
312 // Just continue execution when built with compilers that have no
496 // Clang, GCC, and other compatible compilers used __thread prior to C++11 and
/external/parameter-framework/asio-1.10.6/include/asio/detail/
Dconfig.hpp48 // Support move construction and assignment on compilers known to allow it.
61 // pass a non-member function through a const reference, so for most compilers
78 // Support variadic templates on compilers known to allow it.
80 // Support constexpr on compilers known to allow it.
87 // Compliant C++11 compilers put noexcept specifiers on error_category members.
280 // Handler hooking. Disabled for ancient Borland C++ and gcc compilers.
/external/libcxx/utils/google-benchmark/docs/
DAssemblyTests.md67 `CHECK` lines match against all compilers. (Note: `CHECK-NOT` and
78 inherently non-portable. Different compilers and even different compiler
110 between compilers or compiler versions. A common example of this
143 tests to other architectures and compilers (using `CHECK` prefixes).

12345678910>>...101