| /external/sdv/vsomeip/third_party/boost/asio/doc/ |
| D | platform_macros.qbk | 29 Support alias templates on compilers known to allow it.
120 Support concepts on compilers known to allow them.
127 Support SFINAE use of constant expressions on compilers known to allow it.
134 Support constexpr on compilers known to allow it.
141 Support the co_await keyword on compilers known to allow it.
162 Support automatic type deduction on compilers known to support it.
169 Support default function template arguments on compilers known to allow it.
204 Handler hooking. Disabled for ancient Borland C++ and gcc compilers.
232 Support move construction and assignment on compilers known to allow it.
246 Support noexcept on compilers known to allow it.
[all …]
|
| /external/bazelbuild-rules_go/proto/wkt/ |
| D | BUILD.bazel | 20 compilers = [":any_wrapper"],
34 compilers = [":compiler_plugin_wrapper"],
48 compilers = [":descriptor_wrapper"],
62 compilers = [":duration_wrapper"],
76 compilers = [":empty_wrapper"],
90 compilers = [":field_mask_wrapper"],
104 compilers = [":source_context_wrapper"],
118 compilers = [":struct_wrapper"],
132 compilers = [":timestamp_wrapper"],
146 compilers = [":type_wrapper"],
[all …]
|
| /external/bazelbuild-rules_go/proto/ |
| D | def.bzl | 87 compilers = [attr.compiler]
89 compilers = attr.compilers
90 for compiler in compilers:
99 … #TODO: print("DEPRECATED: compiler attribute on {}, use compilers instead".format(ctx.label))
100 compilers = [ctx.attr.compiler]
102 compilers = ctx.attr.compilers
119 for c in compilers:
174 "compilers": attr.label_list(
192 go_proto_library(compilers = [Label("//proto:go_grpc")], **kwargs)
|
| /external/google-fruit/extras/benchmark/suites/ |
| D | fruit_full.yml | 21 compilers: &compilers
35 compiler: *compilers
52 compiler: *compilers
63 compiler: *compilers
80 compiler: *compilers
92 compiler: *compilers
|
| D | debug.yml | 24 compilers: &compilers
36 compiler: *compilers
66 compiler: *compilers
80 compiler: *compilers
161 compiler: *compilers
173 compiler: *compilers
|
| D | fruit_mostly_full.yml | 21 compilers: &compilers
32 compiler: *compilers
49 compiler: *compilers
60 compiler: *compilers
|
| D | boost_di.yml | 21 compilers: &compilers
38 compiler: *compilers
52 compiler: *compilers
|
| D | fruit_quick.yml | 21 compilers: &compilers
32 compiler: *compilers
50 compiler: *compilers
|
| D | simple_di_full.yml | 24 compilers: &compilers
55 compiler: *compilers
68 compiler: *compilers
|
| D | simple_di_mostly_full.yml | 24 compilers: &compilers
54 compiler: *compilers
68 compiler: *compilers
|
| /external/icu/icu4c/source/ |
| D | runConfigureICU | 39 AIX Use the IBM XL xlclang/xlclang compilers on AIX
40 AIX/GCC Use the GNU gcc/g++ compilers on AIX
41 AIX/OpenXL Use the IBM Open XL ibm-clang_r/ibm-clang++_r compilers on AIX
42 Cygwin Use the GNU gcc/g++ compilers on Cygwin
46 FreeBSD Use the clang/clang++ or GNU gcc/g++ compilers on FreeBSD
47 HP-UX/ACC Use the HP ANSI C/Advanced C++ compilers on HP-UX 11
48 IBMi Use the iCC compilers on IBM i, i5/OS, OS/400
49 Linux Use the default cc/c++ compilers on Linux
50 Linux/clang Use the clang/clang++ compilers on Linux
51 Linux/gcc Use the GNU gcc/g++ compilers on Linux
[all …]
|
| /external/sdv/vsomeip/third_party/boost/move/doc/ |
| D | move.qbk | 24 [section:tested_compilers Tested compilers]
26 [*Boost.Move] has been tested in the following compilers/platforms:
38 don't need C++0x compilers to take advantage of move semanatics. [*Boost.Move] emulates C++0x
39 move semantics in C++03 compilers and allows writing portable code that works optimally in C++03
40 and C++0x compilers.
90 to implement those move semantics not only in compilers with `rvalue references` but also in compil…
177 …d_movable_cpp03 Copyable and movable classes in portable syntax for both C++03 and C++0x compilers]
179 Many aspects of move semantics can be emulated for compilers not supporting `rvalue references`
181 so that it will work both in compilers with rvalue references and those who conform to C++03.
335 C++03 compilers. In compilers with rvalue references perfect forwarding is achieved.
[all …]
|
| /external/cronet/third_party/icu/source/ |
| D | runConfigureICU | 39 AIX Use the IBM XL xlclang/xlclang compilers on AIX
40 AIX/GCC Use the GNU gcc/g++ compilers on AIX
41 AIX/OpenXL Use the IBM Open XL ibm-clang_r/ibm-clang++_r compilers on AIX
42 Cygwin Use the GNU gcc/g++ compilers on Cygwin
46 FreeBSD Use the clang/clang++ or GNU gcc/g++ compilers on FreeBSD
47 HP-UX/ACC Use the HP ANSI C/Advanced C++ compilers on HP-UX 11
48 IBMi Use the iCC compilers on IBM i, i5/OS, OS/400
49 Linux Use the clang/clang++ or GNU gcc/g++ compilers on Linux
50 Linux/gcc Use the GNU gcc/g++ compilers on Linux
54 MacOSX Use the default compilers on MacOS X (Darwin)
[all …]
|
| /external/sdv/vsomeip/third_party/boost/spirit/include/boost/spirit/home/classic/core/ |
| D | config.hpp | 17 // Historically, Spirit supported a lot of compilers, including (to some
18 // extent) poorly conforming compilers such as VC6. Spirit v1.6.x will be
19 // the last release that will support older poorly conforming compilers.
20 // Starting from Spirit v1.8.0, ill conforming compilers will not be
21 // supported. If you are still using one of these older compilers, you can
24 // The reason why Spirit v1.6.x worked on old non-conforming compilers is
26 // workarounds to make these compilers happy. The process takes a lot of
37 // to lesser able compilers; hopefully, fueled by contributions from the
|
| /external/llvm/docs/HistoricalNotes/ |
| D | 2001-04-16-DynamicCompilation.txt | 5 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/sdv/vsomeip/third_party/boost/container_hash/doc/ |
| D | portability.qbk | 11 older compilers don't support argument dependent lookup (ADL) - the mechanism
12 used for customisation. On those compilers custom overloads for `hash_value`
17 so for these compilers the overload should only be declared in the same
42 To make things worse, some compilers which do support ADL won't find
70 Unfortunately, I couldn't declare hash_value as a friend, as some compilers
74 For compilers which don't support ADL, hash_value needs to be defined in the
|
| /external/sdv/vsomeip/third_party/boost/config/doc/ |
| D | guidelines.qbk | 20 Without such configuration information, many current compilers would not work
25 compilers are updated. Ideally, no other files would have to be modified when
29 broken compilers and encouraging non-standard subsets. Adding settings for
38 and are not required in any way to support compilers that do not comply
55 * The intent is to support only compilers which appear on their way to
56 becoming C++ Standard compliant, and only recent releases of those compilers
59 majority of compilers, such as namespaces, exceptions, RTTI, or templates.
74 in one compilers own standard library headers.
135 compilers to test with.[br][br]
141 `config_info` should build and run cleanly for all the compilers in ['`compiler-list`]
[all …]
|
| D | macro_reference.qbk | 53 …efore very strict checks and as a result, other than very recent gcc/clang releases, many compilers
70 …very strict checks, and therefore other than recent gcc/clang releases, many compilers will genrate
163 required by many C++ compilers for embedded platforms). Note that there is
202 most compilers that support SFINAE also support this DR. See also BOOST_NO_SFINAE and BOOST_NO_SFI…
366 however some compilers insist on it, while other issue a bunch of warnings
469 with some compilers.
739 compilers implementing an early draft of the C++11 standard (in particular, incorporating
772 Otherwise use BOOST_NO_SFINAE_EXPR or BOOST_NO_SFINAE which get defined for fewer compilers.
814 [section Macros that allow use of C++11 features with C++03 compilers]
816 The following macros allow use of C++11 features even with compilers that do not yet
[all …]
|
| /external/sdv/vsomeip/third_party/boost/optional/doc/ |
| D | 90_dependencies.qbk | 30 [section Emplace operations in older compilers][#optional_emplace_workaround]
38 On compilers that do not support variadic templates, each of these functions is substituted with tw…
49 On compilers that do not support rvalue references, each of these functions is substituted with thr…
68 …compilers incorrectly treat const lvalues of integral type as rvalues, and create an illegal tempo…
78 Compilers known to have these deficiencies include GCC versions 4.2, 4.3, 4.4, 4.5, 5.1, 5.2; QCC 4…
|
| /external/sdv/vsomeip/third_party/boost/spirit/meta/ |
| D | explicit-failures-markup.xml | 52 Historically, Spirit supported a lot of compilers, including (to some
53 extent) poorly conforming compilers such as VC6. Spirit v1.6.x will be
54 the last release that will support older poorly conforming compilers.
55 Starting from Spirit v1.8.0, ill conforming compilers will not be
56 supported. If you are still using one of these older compilers, you can
60 The reason why Spirit v1.6.x worked on old non-conforming compilers is
62 workarounds to make these compilers happy. The process takes a lot of
74 to lesser able compilers; hopefully, fueled by contributions from the
|
| /external/sdv/vsomeip/third_party/boost/fusion/doc/ |
| D | container.qbk | 89 For C++11 compilers, the variadic function interface has no upper bound.
91 For C++03 compilers, the The variadic form accepts `0` to
242 For C++11 compilers, the variadic function interface has no upper bound.
244 For C++03 compilers, the variadic class interface accepts `0` to
329 For C++11 compilers, the variadic class interface has no upper bound.
331 For C++03 compilers, the variadic class interface accepts `0` to
381 parameter. Interestingly, with modern C++ compilers, this lookup is very
544 For C++11 compilers, the variadic function interface has no upper bound.
546 For C++03 compilers, the variadic class interface accepts `0` to
628 For C++11 compilers, the variadic function interface has no upper bound.
[all …]
|
| /external/sdv/vsomeip/third_party/boost/date_time/xmldoc/ |
| D | buildinfo.xml | 35 …compilers are not capable of utilizing this new system. For those compilers the earlier ("legacy")…
44 …compilers and platforms. However, some compilers and standard libraries have issues. While some of…
78 These compilers support all aspects of the library except <code>wstring/wstream</code>
87 …eam based input output. For these compilers a set of more limited string based input-output is pro…
94 Official support for some older compilers has now been dropped. This includes:
|
| /external/tensorflow/tensorflow/compiler/xla/mlir_hlo/stablehlo/ |
| D | README.md | 9 StableHLO is a portability layer between ML frameworks and ML compilers.
11 TensorFlow, JAX and PyTorch, as well as ML compilers including XLA and IREE.
22 portability layer between ML frameworks and ML compilers. Let's work together
33 ML compilers (XLA and IREE) - ETA: H2 2022.
|
| /external/sdv/vsomeip/third_party/boost/range/doc/ |
| D | portability.qbk | 8 A huge effort has been made to port the library to as many compilers as possible.
10 …iler supports class template partial specialization. For non-conforming compilers there might be a…
13 …compilers cannot do function template ordering properly. In that case one must rely of __range_ite…
|
| /external/tensorflow/tensorflow/compiler/mlir/g3doc/ |
| D | overview.md | 7 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
|