/openbsd-src/gnu/llvm/clang/docs/ |
H A D | ClangOffloadPackager.rst | 14 metadata. We use a custom binary format for bundling all the device images 15 together. The image format is a small header wrapping around a string map. This 22 The binary format is marked by the ``0x10FF10AD`` magic bytes, followed by a 26 format is a serialization of a string map and an image buffer. The binary header 35 | uint8_t | magic | The magic bytes for the binary format (0x10FF10AD) | 37 | uint32_t | version | Version of this format (currently version 1) | 119 array of the :ref:`string entry<table-binary_string>` format. 141 bundled together by simply concatenating them in this format. Because we have 142 the magic bytes and size of each image, we can extract them as-needed. 158 USAGE: clang-offload-packager [options] [all …]
|
H A D | OffloadingDesign.rst | 37 object. A special tool then needs to extract the device code from the fat 59 and extract the device objects. Run the device linking action on the extracted 184 same format as the source location in the :ref:`identifier structure 225 binary format that behaves like a string map. This binary format is used to 268 support a relocatable object format, such as AMDGPU or SPIR-V, or if the user 435 $ clang++ -fopenmp -fopenmp-targets=nvptx64 -O3 zaxpy.cpp -c 450 Compiling this file again will invoke the ``clang-linker-wrapper`` utility to 451 extract and link the device code stored at the section named 458 $ clang++ -fopenmp -fopenmp-targets=nvptx64 zaxpy.o -o zaxpy 461 We can see the steps created by clang to generate the offloading code using the [all …]
|
H A D | LibASTMatchers.rst | 22 interface to extract attributes, source locations, or any other information 56 how to dump a translation unit's AST into a human readable format. 84 <https://clang.llvm.org/doxygen/classclang_1_1ast__matchers_1_1MatchFinder_1_1MatchCallback.html>`_. 119 <https://clang.llvm.org/doxygen/ASTMatchersMacros_8h.html>`_.
|
H A D | PCHInternals.rst | 12 Using Precompiled Headers with ``clang`` 15 The Clang compiler frontend, ``clang -cc1``, supports two command line options 18 To generate PCH files using ``clang -cc1``, use the option `-emit-pch`: 22 $ clang -cc1 test.h -emit-pch -o test.h.pch 24 This option is transparently used by ``clang`` when generating PCH files. The 32 $ clang -cc1 -include-pch test.h.pch test.c -o test.s 65 AST file format required for modules are discussed in the section on 72 compressed bitstream as `LLVM's bitcode file format 127 An AST file produced by clang is an object file container with a ``clangast`` 137 within `LLVM's bitstream format <https://llvm.org/docs/BitCodeFormat.html>`_. [all …]
|
H A D | ClangFormattedStatus.rst | 132 * - clang/bindings/python/tests/cindex/INPUTS 137 * - clang/docs/analyzer/checkers 142 * - clang/examples/AnnotateFunctions 147 * - clang/examples/Attribute 152 * - clang/examples/CallSuperAttribute 157 * - clang/examples/PluginsOrder 162 * - clang/examples/PrintFunctionNames 167 * - clang/include/clang/Analysis 172 * - clang/include/clang/Analysis/Analyses 177 * - clang/include/clang/Analysis/DomainSpecific [all …]
|
/openbsd-src/gnu/llvm/llvm/docs/ |
H A D | XRay.rst | 57 enabling the ``-fxray-instrument`` flag in your clang invocation. 63 clang -fxray-instrument ... 71 clang -fxray-instrument -fxray-instruction-threshold=1 ... 80 [[clang::xray_always_instrument]] void always_instrumented(); 82 [[clang::xray_never_instrument]] void never_instrumented(); 89 Library`_ or use ``clang`` to link it in automatically with the 92 `libclang_rt.xray-{arch}` where `{arch}` is the mnemonic supported by clang 128 logging from a file. The file's format is described below: 140 These files can be provided through the ``-fxray-attr-list=`` flag to clang. 148 instrumentation points. When you use ``clang`` to link your binaries and the [all …]
|
H A D | SourceLevelDebugging.rst | 12 information in LLVM. It describes the :ref:`actual format that the LLVM debug 13 information takes <format>`, which is useful for those interested in creating 49 :ref:`implementation-defined format <ccxx_frontend>` (the C/C++ front-end 69 the Microsoft debug info format, which is usable with Microsoft debuggers such 70 as Visual Studio and WinDBG. LLVM's debug information format is mostly derived 135 Debugging information format 299 In order to handle this, the LLVM debug format uses the metadata attached to 316 default in clang. 351 …!0 = !DICompileUnit(language: DW_LANG_C99, file: !1, producer: "clang version 3.7.0 (trunk 231150)… 361 !10 = !{!"clang version 3.7.0 (trunk 231150) (llvm/trunk 231154)"} [all …]
|
H A D | TestingGuide.rst | 75 result and print it on the standard output in a textual format suitable for 148 If you have `Clang <https://clang.llvm.org/>`_ checked out and built, you 304 C/C++, or clang/clang++ (IR checks) 323 using ``split-file`` to extract them. For example, 691 ``%clang``
|
H A D | LangRef.rst | 477 On targets that use the ELF object file format, default visibility 1514 have a particular format. Specifically, it must begin with a sequence of 1520 makes the format of the prologue data highly target dependent. 2019 `SafeStack <https://clang.llvm.org/docs/SafeStack.html>`_ 2350 protected by MTE. This attribute is added by clang when 2637 :ref:`stackmap entry <statepoint-stackmap-format>`. See the intrinsic description 2643 A ``"clang.arc.attachedcall"`` operand bundle on a call indicates the call is 2649 ``@llvm.objc.clang.arc.noop.use`` unless the called function's return type is 2656 call ptr @foo() [ "clang.arc.attachedcall"(ptr @objc_retainAutoreleasedReturnValue) ] 2657 call ptr @foo() [ "clang.arc.attachedcall"(ptr @objc_unsafeClaimAutoreleasedReturnValue) ] [all …]
|
/openbsd-src/gnu/llvm/llvm/utils/release/ |
H A D | build_llvm_release.bat | 50 REM 7zip versions 21.x and higher will try to extract the symlinks in 77 REM Visual Studio 2019 SDK and Nuget (for the clang-format plugin), 152 -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;lld;compiler-rt;lldb;openmp" 194 -DLLDB_TEST_COMPILER=%stage0_bin_dir%/clang.exe ^ 203 REM ninja check-clang || ninja check-clang || ninja check-clang || exit /b 1 206 REM ninja check-clang-tools || ninja check-clang-tools || ninja check-clang-tools || exit /b 1 213 -DCMAKE_C_COMPILER=%stage0_bin_dir%/clang-cl.exe ^ 214 -DCMAKE_CXX_COMPILER=%stage0_bin_dir%/clang-cl.exe ^ 225 REM ninja check-clang || ninja check-clang || ninja check-clang || exit /b 1 228 REM ninja check-clang-tools || ninja check-clang-tools || ninja check-clang-tools || exit /b 1 [all …]
|
/openbsd-src/gnu/llvm/lld/ELF/ |
H A D | Options.td | 157 def eb: F<"EB">, HelpText<"Select the big-endian format in OUTPUT_FORMAT">; 158 def el: F<"EL">, HelpText<"Select the little-endian format in OUTPUT_FORMAT">; 222 defm format: Eq<"format", "Change the input format of the inputs following this option">, 307 defm oformat: EEq<"oformat", "Specify the binary format for the output object file">, 317 EEq<"pack-dyn-relocs", "Pack dynamic relocations in the given format">, 470 "Warn about backward symbol references to extract archive members", 471 "Do not warn about backward symbol references to extract archive members (default)">; 498 def why_extract: JJ<"why-extract=">, HelpText<"Print to a file about why archive members are extrac… 526 def: Separate<["-"], "b">, Alias<format>, HelpText<"Alias for --format">; 592 def opt_remarks_format: Separate<["--"], "opt-remarks-format">, [all …]
|
/openbsd-src/gnu/llvm/lldb/docs/use/ |
H A D | variable.rst | 100 type format 121 Type formats enable you to quickly override the default format for displaying 125 hex, you can add a format to the int type. 131 (lldb) type format add --format hex int 135 The ``--format`` (which you can shorten to -f) option accepts a :doc:`format 137 new format applied. 141 can add a format just to that typedef by using type format add with the name 162 (lldb) type format add -f hex A 163 (lldb) type format add -f uint8_t[] C 181 (lldb) type format add -C no -f hex A [all …]
|
/openbsd-src/gnu/llvm/clang/include/clang/Basic/ |
H A D | AttrDocs.td | 9 // To test that the documentation builds cleanly, you must run clang-tblgen to 15 // To run clang-tblgen to generate the .rst file: 16 // clang-tblgen -gen-attr-docs -I <root>/llvm/tools/clang/include 17 // <root>/llvm/tools/clang/include/clang/Basic/Attr.td -o 18 // <root>/llvm/tools/clang/docs/AttributeReference.rst 22 // Windows (from within the clang\docs directory): 24 // Non-Windows (from within the clang\docs directory): 30 NOTE: This file is automatically generated by running clang-tblgen 244 <https://clang.llvm.org/docs/BlockLanguageSpec.html>`, the same restriction 459 ``stream`` type). Kernel parameters types are extract from the ``__init`` method [all …]
|
/openbsd-src/gnu/llvm/lldb/docs/resources/ |
H A D | test.rst | 18 is the test format that uses ``RUN:`` lines. `FileCheck 128 shared across tests, we extract it into a utility in ``lldbutil``. It's always 379 @skipIf(compiler=no_match("clang")) 387 This tells the test harness that unless we are running "linux" and clang version equal & above 8.0,… 439 built with a custom version of clang, do: 443 $ cmake -DLLDB_TEST_USER_ARGS="-A i386 -C /path/to/custom/clang" -G Ninja 642 # Path to release clang.exe 643 -C d:\src\llvmbuild\ninja_release\bin\clang.exe 651 …AGS -u CFLAGS --enable-crash-dialog -C d:\src\llvmbuild\ninja_release\bin\clang.exe -p TestPaths.p…
|
/openbsd-src/gnu/llvm/llvm/docs/TableGen/ |
H A D | BackEnds.rst | 251 format. A helper script, utils/TableGen/tdtags, provides an easier-to-use 427 Generate arm_neon.h for clang. 432 Generate ARM NEON sema support for clang. 437 Generate ARM NEON tests for clang. 481 this data. The format described here corresponds to version 1. 580 ``printable`` field can be used to extract a representation of them 710 can format the C++ initializers in the emitted table. It can deduce ``bit``,
|
/openbsd-src/gnu/llvm/clang/include/clang/Driver/ |
H A D | Options.td | 1 //===--- Options.td - Options for clang -----------------------------------===// 9 // This file defines the options accepted by clang. 39 // clang and clang-cl modes. 46 // CC1Option - This option should be accepted by clang -cc1. 49 // CC1AsOption - This option should be accepted by clang -cc1as. 117 def clang_i_Group : OptionGroup<"<clang i group>">, Group<i_Group>, DocFlatten; 143 def f_clang_Group : OptionGroup<"<f (clang-only) group>">, 231 // Temporary groups for clang options which we know we don't support, 233 def clang_ignored_f_Group : OptionGroup<"<clang ignored f group>">, 235 def clang_ignored_m_Group : OptionGroup<"<clang ignored m group>">, [all …]
|
/openbsd-src/gnu/llvm/clang/lib/CodeGen/ |
H A D | CodeGenModule.cpp | 74 using namespace clang; 468 static void setVisibilityFromDLLStorageClass(const clang::LangOptions &LO, in setVisibilityFromDLLStorageClass() 2391 Type = llvm::mdconst::extract<llvm::ConstantInt>(MD->getOperand(0)); in finalizeKCFITypes() 2648 void CodeGenModule::EmitModuleInitializers(clang::Module *Primary) { in EmitModuleInitializers() 2679 llvm::SetVector<clang::Module *> LinkModules; in EmitModuleLinkOptions() 2680 llvm::SmallPtrSet<clang::Module *, 16> Visited; in EmitModuleLinkOptions() 2681 SmallVector<clang::Module *, 16> Stack; in EmitModuleLinkOptions() 2697 clang::Module *Mod = Stack.pop_back_val(); in EmitModuleLinkOptions() 2886 ID.Add(cast<clang::ConstantExpr>(E)->getAPValueResult()); in EmitAnnotationArgs() 2896 const auto *CE = cast<clang::ConstantExpr>(E); in EmitAnnotationArgs() [all …]
|
/openbsd-src/gnu/usr.bin/perl/pod/ |
H A D | perlhacktips.pod | 154 void greet(char *file, unsigned int line, char *format, ...); 259 C99 format strings in C<< <inttypes.h> >> 878 intelligence, but for many types the right format is available as with 897 Also remember that the C<%p> format really does require a void pointer: 1093 version 2.17. They won't allow a C<%.s> format with a precision to 1480 Download the pmd-bin-X.Y.zip () from the SourceForge site, extract the 1652 sh Configure -des -Dcc=clang \ 1661 =item * -Dcc=clang 1663 This should be replaced by the full path to your clang executable if it
|
/openbsd-src/lib/libz/ |
H A D | ChangeLog | 59 - Add address checking in clang to -w option of configure 75 - Use a macro for the printf format of big_t in enough.c 107 - Check for cc masquerading as gcc or clang in configure 248 - Recognize clang as gcc 433 - Fix CROSS_PREFIX executable testing, CHOST extract, mingw* [Torok] 796 - Add error return to gzread() for format or i/o error [Levin] 1029 - Fix printf format in example.c 1059 - Improve setting of zlib format compression level flags 1142 - Add contrib/puff/ simple inflate for deflate format description 1411 - mention in README that the zlib format is now RFC1950
|
/openbsd-src/gnu/llvm/llvm/lib/Target/X86/ |
H A D | X86InstrAVX512.td | 90 // 8-bit compressed displacement tuple/subvector format. This is only 979 // Codegen pattern with the alternative types extract VEC128 from VEC256 987 // Codegen pattern with the alternative types extract VEC128 from VEC512 994 // Codegen pattern with the alternative types extract VEC256 from VEC512 1003 // A 128-bit extract from bits [255:128] of a 512-bit vector should use a 1004 // smaller extract to enable EVEX->VEX. 1036 // A 128-bit extract from bits [255:128] of a 512-bit vector should use a 1037 // smaller extract to enable EVEX->VEX. 1176 // vextractps - extract 32 bits from XMM 3752 // available. Use a 512-bit operation and extract. [all …]
|
/openbsd-src/share/dict/ |
H A D | web2 | 37041 clang 67368 extract 72685 format
|