| /llvm-project-15.0.7/lldb/packages/Python/lldbsuite/test/ |
| H A D | decorators.py | 409 compilers=None, argument
415 compiler=compilers,
426 compilers,
472 def expectedFlakeyOS(oslist, bugnumber=None, compilers=None): argument
475 self.expectedCompiler(compilers))
479 def expectedFlakeyDarwin(bugnumber=None, compilers=None): argument
485 compilers)
488 def expectedFlakeyFreeBSD(bugnumber=None, compilers=None): argument
492 def expectedFlakeyLinux(bugnumber=None, compilers=None): argument
493 return expectedFlakeyOS(['linux'], bugnumber, compilers)
[all …]
|
| /llvm-project-15.0.7/llvm/docs/HistoricalNotes/ |
| H A 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
|
| H A D | 2001-06-20-.NET-Differences.txt | 18 said that SGI and other commercial compilers have included options to export
24 optimize modules from multiple different compilers. (Also, of course, they
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/modernize/ |
| H A D | use-override.rst | 10 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:
|
| /llvm-project-15.0.7/third-party/benchmark/docs/ |
| H A D | AssemblyTests.md | 67 `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).
|
| /llvm-project-15.0.7/lldb/examples/test/ |
| H A D | .lldbtest-config | 3 compilers = ["gcc", "llvm-gcc"]
|
| H A D | usage-config | 3 # of architectures and compilers.
|
| H A D | usage-lldb-loggings | 39 compilers=['clang']
103 compilers=['clang']
|
| /llvm-project-15.0.7/llvm/test/Bitcode/ |
| H A D | apple-clang-700-compat.test | 2 ; compilers. However, it does produce valid bitcode which should parse without
|
| /llvm-project-15.0.7/clang/include/clang/Basic/ |
| H A D | TargetCXXABI.def | 29 /// many compilers, including Clang and GCC.
55 /// in the compilers that iOS was launched with.
120 /// compatible compilers).
|
| /llvm-project-15.0.7/llvm/ |
| H A D | README.txt | 5 a toolkit for the construction of highly optimized compilers,
|
| /llvm-project-15.0.7/openmp/runtime/ |
| H A D | README.txt | 107 The following compilers are known to do compatible code generation for
109 http://clang-omp.github.io/ ), Intel compilers, GCC. See the documentation
|
| /llvm-project-15.0.7/llvm/utils/gn/secondary/compiler-rt/lib/profile/ |
| H A D | BUILD.gn | 22 # aggregate initializers. All other compilers accept this, though.
|
| /llvm-project-15.0.7/llvm/test/tools/llvm-objdump/ELF/ |
| H A D | relocations-in-nonreloc.test | 8 ## Non-SHF_ALLOC relocations are usually generated by compilers.
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/readability/ |
| H A D | redundant-member-init.rst | 31 within copy constructors, since some compilers issue warnings/errors when
|
| /llvm-project-15.0.7/compiler-rt/test/BlocksRuntime/ |
| H A D | testfilerunner.m | 582 printf(" -clang use the clang and clang++ compilers\n");
588 …printf("%s will compile and run individual test files under a variety of compilers, c, obj-c, c++,…
589 printf(" .c files are compiled with all four compilers\n");
590 printf(" .m files are compiled with objc and objc++ compilers\n");
591 printf(" .C files are compiled with c++ and objc++ compilers\n");
593 …printf("(actually all forms of extensions recognized by the compilers are honored, .cc, .c++ etc.)…
595 …"Further they should be able to be compiled and run with GC on or off and by the C++ compilers\n");
599 printf(" C++ restricts the test to only be run by c++ and objc++ compilers\n");
|
| /llvm-project-15.0.7/flang/docs/ |
| H A D | index.md | 7 independent Fortran compilers. LLVM Flang is under active development. While it
|
| /llvm-project-15.0.7/lld/test/ELF/ |
| H A D | reloc-sec-before-relocated.test | 3 ## Normally it is not what compilers would emit, but some custom tools might
|
| /llvm-project-15.0.7/compiler-rt/lib/tsan/rtl-old/ |
| H A D | tsan_update_shadow_word.inc | 12 // If we wrap this body into a function, compilers (both gcc and clang)
|
| /llvm-project-15.0.7/llvm/lib/Target/SystemZ/ |
| H A D | SystemZProcessors.td | 11 // For compatibility with other compilers on the platform, each model can
|
| /llvm-project-15.0.7/libcxx/docs/ |
| H A D | index.rst | 100 Libc++ aims to support common compilers that implement the C++11 Standard. In order to strike a
102 velocity, libc++ drops support for older compilers as newer ones are released.
131 for all the platforms and compilers that we claim to support. If a platform or compiler
|
| /llvm-project-15.0.7/polly/lib/External/ |
| H A D | isl_config.h.cmake | 4 /* most gcc compilers know a function __attribute__((__warn_unused_result__)) */
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | AdvancedBuilds.rst | 78 Setting up these compilers requires a lot of options. To simplify the
172 In the ancient lore of compilers non-determinism is like the multi-headed hydra.
191 After the build you can compare the stage2 & stage3 compilers.
|
| H A D | index.rst | 10 industrial strength compilers to specialized JIT applications to small
|
| /llvm-project-15.0.7/llvm/lib/Support/BLAKE3/ |
| H A D | CMakeLists.txt | 24 # different compilers, and they build more quickly."
|