/openbsd-src/gnu/llvm/llvm/utils/gn/secondary/clang/tools/clang-format/ |
H A D | BUILD.gn | 1 executable("clang-format") { 4 "//clang/lib/Basic", 5 "//clang/lib/Format", 6 "//clang/lib/Rewrite", 7 "//clang/lib/Tooling/Core", 11 "//clang/lib/AST/", 12 "//clang/lib/Frontend/", 13 "//clang/lib/Sema/",
|
/openbsd-src/gnu/llvm/llvm/utils/ |
H A D | update_cc_test_checks.py | 39 json_dump_args = [args.clang] + clang_args + ['-fsyntax-only', '-o', '-'] 118 common.debug('line {}: found function {}'.format(line+1, func), file=sys.stderr) 131 if not args.clang: 133 args.clang = 'clang' 135 args.clang = os.path.join(args.llvm_bin, 'clang') 143 def find_executable(executable): argument 144 _, ext = os.path.splitext(executable) 146 executable = executable + '.exe' 148 return shutil.which(executable) 178 if not find_executable(args.clang): [all …]
|
/openbsd-src/gnu/llvm/clang/docs/ |
H A D | OffloadingDesign.rst | 33 The goal of offloading compilation is to create an executable device image that 34 can be run on the target device. OpenMP offloading creates executable images by 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 257 create an executable device image. This is done using a Clang tool, see 268 support a relocatable object format, such as AMDGPU or SPIR-V, or if the user 277 offload code on the device. We use the :ref:`linked device executable <Device 360 describes all device images available in the executable or shared library. It 435 $ clang++ -fopenmp -fopenmp-targets=nvptx64 -O3 zaxpy.cpp -c 439 removed from the final executable or shared library by the linker. [all …]
|
H A D | JSONCompilationDatabase.rst | 5 This document describes a format for specifying how to replay single 33 ``-MJ argument <clang -MJ\<arg>>``. You can concatenate those 51 python bindings also support this (since clang 3.2); see 70 …"arguments": ["/usr/bin/clang++", "-Irelative", "-DSOMEDEF=With spaces, quotes and \\-es.", "-c", … 74 …"command": "/usr/bin/clang++ -Irelative -DSOMEDEF=\"With spaces, quotes and \\-es.\" -c -o file.o … 92 ``arguments[0]`` should be the executable name, such as ``clang++``.
|
H A D | AddressSanitizer.rst | 17 * Use-after-return (clang flag ``-fsanitize-address-use-after-return=(never|runtime|always)`` defau… 20 * Use-after-scope (clang flag ``-fsanitize-address-use-after-scope``) 35 AddressSanitizer run-time library should be linked to the final executable, so 36 make sure to use ``clang`` (not ``ld``) for the final link step. When linking 54 % clang++ -O1 -g -fsanitize=address -fno-omit-frame-pointer example_UseAfterFree.cc 61 % clang++ -O1 -g -fsanitize=address -fno-omit-frame-pointer -c example_UseAfterFree.cc 63 % clang++ -g -fsanitize=address example_UseAfterFree.o 79 executable. (You can find the library by searching for dynamic libraries with 81 try to re-exec. Also keep in mind that when moving the executable to another machine, 186 path of the file relative to the location of your executable. [all …]
|
H A D | UsersManual.rst | 18 `Clang Web Site <https://clang.llvm.org>`_ or the `LLVM Web 25 `Clang Static Analyzer <https://clang-analyzer.llvm.org>`_, please see its web 55 Clang also provides an alternative driver, :ref:`clang-cl`, that is designed 164 output format of the diagnostics that it generates. 260 .. option:: -fdiagnostics-format=clang/msvc/vi 262 Changes diagnostic output format to better match IDEs and command line tools. 264 This option controls the output format of the filename, line number, 268 **clang** (default) 317 For example, a format string warning will produce these three 332 .. option:: -f[no-]save-optimization-record[=<format>] [all …]
|
H A D | SourceBasedCodeCoverage.rst | 11 This document explains how to use clang's source-based code coverage feature. 62 % clang++ -fprofile-instr-generate -fcoverage-mapping foo.cc -o foo 132 …% clang++ -fprofile-instr-generate -fcoverage-mapping -mllvm -runtime-counter-relocation foo.cc -o… 267 least once. Only executable lines within function bodies are considered to be 292 profile format. Raw profiles may be dependent on the specific compiler 297 These formats are not forwards-compatible: i.e, a tool which uses format 298 version X will not be able to understand format version (X+k). 300 * Tools must also retain **backwards** compatibility with the format of the 304 * The JSON coverage export format has a (major, minor, patch) version triple. 330 library and executable. When the linker finds a definition of this symbol, it [all …]
|
H A D | SanitizerCoverage.rst | 56 // binary (executable or DSO). The callback will be called at least 100 clang++ -g -fsanitize-coverage=trace-pc-guard trace-pc-guard-example.cc -c 101 clang++ trace-pc-guard-cb.cc trace-pc-guard-example.o -fsanitize=address 411 The allowlist and blocklist format is similar to that of the sanitizer blocklist format. 442 Be careful that the paths of source files are matched exactly as they are provided on the clang 471 % clang++ -g cov.cc -fsanitize=address -fsanitize-coverage=trace-pc-guard 483 Every time you run an executable instrumented with SanitizerCoverage 485 If the executable is dynamically linked against instrumented DSOs, 488 Sancov data format 491 The format of ``*.sancov`` files is very simple: the first 8 bytes is the magic, [all …]
|
H A D | ReleaseNotes.rst | 31 latest release, please see the `Clang Web Site <https://clang.llvm.org>`_ or the 48 - Clang's resource directory path previously included the full clang version. 50 ``$prefix/lib/clang/$CLANG_MAJOR_VERSION`` and can be queried using 51 ``clang -print-resource-dir``, just like before. 99 clang-cl), the compiler will now propagate dllimport/export declspecs in 108 template<> void S<int>::f() {} // clang-cl will now dllexport this. 111 cause errors for code which clang-cl would previously accept, for example: 291 <https://clang.llvm.org/docs/Modules.html#use-declaration>`_ are now 431 - When loading default configuration files, clang now unconditionally uses 433 rather than the executable prefix. The respective configuration files are [all …]
|
/openbsd-src/gnu/llvm/llvm/utils/lit/lit/llvm/ |
H A D | config.py | 46 self.lit_config.note("using lit tools: {}".format(path)) 269 def get_clang_builtin_include_dir(self, clang): argument 273 [clang, '-print-file-name=include']) 276 print(clang) 278 "Couldn't find the include dir for Clang ('%s')" % clang) 288 def get_clang_has_lsan(self, clang, triple): argument 289 if not clang: 295 clang_binary = clang.split()[0] 420 self.config.substitutions.append(('%python', '"%s"' % (sys.executable))) 450 message = "couldn't find '{}' program".format(name) [all …]
|
/openbsd-src/gnu/llvm/lld/docs/ |
H A D | WebAssembly.rst | 10 Object file format 13 The WebAssembly object file format used by LLVM and LLD is specified as part of 16 This is the object format that the llvm will produce when run with the 48 When building an executable, export any non-hidden symbols. By default only 107 generate an error if they cannot be resolved statically. For clang/llvm 171 When building an executable, only the entry point (``_start``) and symbols with 174 in turn can be set using ``__attribute__((export_name))`` clang attribute. 181 used to export symbols in the executable which are marked as 194 ``import_name`` and/or ``import_module`` clang attributes which signals that
|
H A D | index.rst | 47 all you have to do to do LTO is to pass the ``-flto`` option to clang. 48 Then clang creates object files not in the native object file format 49 but in LLVM bitcode format. LLD reads bitcode object files, compile 56 non-executable by default to tighten security. 70 clang dbg 1.67 GiB 104.03s 34.18s 23.49s 14.82s … 88 under ``tools`` directory just like you probably did for clang. For the 117 If you don't want to change the system setting, you can use clang's
|
/openbsd-src/gnu/llvm/llvm/docs/ |
H A D | CFIVerify.rst | 30 - Integration tests, present in "/llvm/tools/clang/test/LLVMCFIVerify". These 31 integration tests are part of clang as part of a continuous integration 57 This tool will disassemble binaries and DSO's from their machine code format and 85 Only machine code sections that are marked as executable will be subject to this 86 analysis. Non-executable sections do not require analysis as any execution
|
H A D | DebuggingJITedCode.rst | 19 in-memory object file that contains the debug information in DWARF format. 102 > $BINPATH/clang -g -S -emit-llvm --target=x86_64-unknown-unknown-elf showdebug.c 105 Current executable set to '/workspaces/llvm-project/build/bin/lli' (x86_64).
|
H A D | SymbolizerMarkupFormat.rst | 11 This document defines a text format for log messages that can be processed by a 15 markup format defined here to identify pieces of information that should be 28 This format identifies markup elements with a syntax that is both simple and 45 This format assumes that the symbolizing filter processes intact whole lines. If 55 This format assumes that the symbolizing filter processes a coherent stream of 74 (executable, shared library, loadable module, or driver module). The linker 87 The markup format supports a restricted subset of ANSI X3.64 SGR (Select Graphic 320 identifier are outside the scope of the markup format per se. In general it 335 `SanitizerCoverage <https://clang.llvm.org/docs/SanitizerCoverage.html>`_. 416 executable. The symbolizing filter can use this information to guess whether [all …]
|
/openbsd-src/gnu/llvm/lldb/source/Core/ |
H A D | CoreProperties.td | 7 …executable are always checked first for separate debug info files. Then depending on this setting:… 12 def ClangModulesCachePath: Property<"clang-modules-cache-path", "FileSpec">, 15 Desc<"The path to the clang modules cache directory (-fmodules-cache-path).">; 51 def DisassemblyFormat: Property<"disassembly-format", "FormatEntity">, 54 Desc<"The default disassembly format string to use when disassembling instruction sequences.">; 55 def FrameFormat: Property<"frame-format", "FormatEntity">, 58 …Desc<"The default frame format string to use when displaying stack frame information for threads."… 109 …n a color-enabled terminal, use the ANSI terminal code specified in this format at the immediately… 113 …n a color-enabled terminal, use the ANSI terminal code specified in this format immediately after … 117 …n a color-enabled terminal, use the ANSI terminal code specified in this format at the immediately… [all …]
|
/openbsd-src/gnu/llvm/lld/ELF/ |
H A D | Options.td | 97 "Do not allow unresolved references in shared libraries (default when linking an executable)">; 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">; 190 "Mark executable sections unreadable", 191 "Mark executable sections readable (default)">; 198 "(executable) Put matched symbols in the dynamic symbol table. " 222 defm format: Eq<"format", "Change the input format of the inputs following this option">, 290 HelpText<"Retain the executable output file whenever it is still usable">; 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">, [all …]
|
/openbsd-src/gnu/llvm/llvm/docs/CommandGuide/ |
H A D | llvm-cov.rst | 16 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation 85 count is shown as ``-`` if a line does not contain any executable code. If 200 *BIN* may be an executable, object file, dynamic library, or archive (thin or 205 ``clang`` use the ``-fprofile-instr-generate`` and ``-fcoverage-mapping`` 206 flags. If linking with the ``clang`` driver, pass ``-fprofile-instr-generate`` 209 The coverage information is stored in the built executable or library itself, 213 typically called ``default.profraw``, which can be converted to a format that 282 .. option:: -format=<FORMAT> 284 Use the specified output format. The supported formats are: "text", "html". 289 only supported for the html format. [all …]
|
H A D | llvm-objdump.rst | 30 Disassemble all executable sections found in the input files. On some 70 Display format-specific file headers. 80 .. option:: --raw-clang-ast 82 Dump the raw binary contents of the clang AST section. 104 Display the version of the :program:`llvm-objdump` executable. Does not stack 150 .. option:: --debug-vars=<format> 153 alongside disassembly. ``format`` may be ``unicode`` or ``ascii``, defaulting 199 Do not use hex format for immediate values in disassembly output. 222 Use hex format when printing immediate values in disassembly output (default). 418 Display only the first format specific file header.
|
H A D | llc.rst | 16 through a native assembler and linker to generate a native executable. 27 assembly language format (``.ll``) or the LLVM bitcode format (``.bc``). 55 :program:`clang`.
|
/openbsd-src/gnu/llvm/lldb/source/Target/ |
H A D | TargetProperties.td | 39 …placement. A common pattern is to use source-map in conjunction with the clang -fdebug-prefix-map… 45 …Desc<"Executable search paths to use when locating executable files whose paths don't match the lo… 49 def ClangModuleSearchPaths: Property<"clang-module-search-paths", "FileSpecList">, 52 def AutoImportClangModules: Property<"auto-import-clang-modules", "Boolean">, 76 def MaxZeroPaddingInFloatFormat: Property<"max-zero-padding-in-float-format", "UInt64">, 96 …t passed to the program in the argument array which can be different from the executable itself.">; 99 …Desc<"A list containing all the arguments to be passed to the executable when it is run. Note that… 102 …Desc<"A list of user provided environment variables to be passed to the executable's environment, … 111 Desc<"The file/path to be used by the executable program for reading its standard input.">; 114 Desc<"The file/path to be used by the executable program for writing its standard output.">; [all …]
|
/openbsd-src/gnu/llvm/clang/docs/CommandGuide/ |
H A D | clang.rst | 1 clang, clang++, clang-cpp - the Clang C, C++, and Objective-C compiler 7 :program:`clang` [*options*] *filename ...* 12 :program:`clang` is a C, C++, and Objective-C compiler which encompasses 20 The clang executable is actually a small driver which controls the overall 56 executable or dynamic library. The output of this stage is typically called 63 the same driver. Please see <https://clang-analyzer.llvm.org> for more details 92 linker is run to combine the results into an executable or shared library. 437 option transparently switches the Clang module format to object file 502 assembly files, otherwise this generates LLVM bitcode format object files 519 the executable as well as generating the ``.dSYM`` bundle using :manpage:`dsymutil(1)`. [all …]
|
/openbsd-src/gnu/llvm/clang/ |
H A D | CMakeLists.txt | 66 option(CLANG_ENABLE_BOOTSTRAP "Generate the clang bootstrap target" OFF) 159 # This allows disabling clang's XML dependency even if LLVM finds libxml2. 160 # By default, clang depends on libxml2 if LLVM does. 183 "Colon separated list of directories clang will search for headers.") 195 "Enable IEEE binary128 as default long double format on PowerPC Linux.") 198 "Whether clang should use a new process for the CC1 invocation") 243 "Default objcopy executable to use.") 260 set(CLANG_VENDOR_UTI "org.llvm.clang" CACHE STRING 308 ${CMAKE_CURRENT_SOURCE_DIR}/include/clang/Basic/Version.inc.in 309 ${CMAKE_CURRENT_BINARY_DIR}/include/clang/Basic/Version.inc) [all …]
|
/openbsd-src/gnu/llvm/lldb/docs/resources/ |
H A D | test.rst | 18 is the test format that uses ``RUN:`` lines. `FileCheck 77 tests almost always require a fully functional executable. This enables testing 218 **Don't unnecessarily launch the test executable.** 222 of the test executable. 225 everything that represents information about the executable and its 241 Including external headers slows down the compilation of the test executable 280 test executable and running the process to a breakpoint). Using these 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: [all …]
|
/openbsd-src/gnu/llvm/llvm/tools/llvm-objdump/ |
H A D | ObjdumpOpts.td | 58 HelpText<"Disassemble all executable sections found in the input files">; 140 def raw_clang_ast : Flag<["--"], "raw-clang-ast">, 141 HelpText<"Dump the raw binary contents of the clang AST section">; 148 HelpText<"Use hex format for immediate values (default)">; 151 HelpText<"Do not use hex format for immediate values">; 155 HelpText<"Display format specific file headers">; 249 HelpText<"Display only the first format specific file header">,
|