/openbsd-src/gnu/llvm/clang/include/clang/Tooling/Refactoring/ |
H A D | AtomicChange.h | 24 namespace clang { 88 llvm::Error replace(const SourceManager &SM, const CharSourceRange &Range, 94 llvm::Error replace(const SourceManager &SM, SourceLocation Loc, 137 clang::tooling::Replacements Replaces); 163 format::FormatStyle Style = format::getNoStyle();
|
/openbsd-src/gnu/llvm/clang/lib/Tooling/Refactoring/ |
H A D | AtomicChange.cpp | 14 LLVM_YAML_IS_SEQUENCE_VECTOR(clang::tooling::AtomicChange) 29 const clang::tooling::AtomicChange &E) in NormalizedAtomicChange() 36 clang::tooling::AtomicChange denormalize(const llvm::yaml::IO &) { in denormalize() 45 std::vector<clang::tooling::Replacement> Replaces; 67 template <> struct MappingTraits<clang::tooling::AtomicChange> { 68 static void mapping(IO &Io, clang::tooling::AtomicChange &Doc) { in mapping() 69 MappingNormalization<NormalizedAtomicChange, clang::tooling::AtomicChange> in mapping() 83 namespace clang { namespace 109 const clang::tooling::Replacements &Replaces) { in getRangesForFormating() 113 std::vector<clang::tooling::Range> Ranges; in getRangesForFormating() [all …]
|
/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') 178 if not find_executable(args.clang): 187 [args.clang, '-print-file-name=include']).decode().strip() 207 raw_tool_output = common.invoke_tool(args.clang, clang_args, filename) 270 exec_args = [i.replace(s, subs[s]) if s in i else i for i in exec_args] 278 clang_args = [i.replace(s, subs[s]) if s in i else i for i in clang_args] [all …]
|
/openbsd-src/gnu/llvm/llvm/docs/ |
H A D | FuzzingLLVM.rst | 20 clang-fuzzer 28 __ https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj-llvm+clang-fuzzer 30 clang-proto-fuzzer 36 This fuzzer accepts clang command line options after `ignore_remaining_args=1`. 37 For example, the following command will fuzz clang with a higher optimization 42 % bin/clang-proto-fuzzer <corpus-dir> -ignore_remaining_args=1 -O3 44 clang-format-fuzzer 47 A |generic fuzzer| that runs clang-format_ on C++ text fragments. Some of the 51 .. _clang-format: https://clang.llvm.org/docs/ClangFormat.html 53 __ https://bugs.chromium.org/p/oss-fuzz/issues/list?q=proj-llvm+clang-format-fuzzer [all …]
|
H A D | LibFuzzer.rst | 73 … E.g. if your target can parse several data formats, split it into several targets, one per format. 86 …clang -g -O1 -fsanitize=fuzzer mytarget.c # Builds the fuzz target w/o san… 87 …clang -g -O1 -fsanitize=fuzzer,address mytarget.c # Builds the fuzz target with AS… 88 …clang -g -O1 -fsanitize=fuzzer,signed-integer-overflow mytarget.c # Builds the fuzz target with a … 89 …clang -g -O1 -fsanitize=fuzzer,memory mytarget.c # Builds the fuzz target with MS… 98 clang -fsanitize=fuzzer-no-link mytarget.c 208 The plan is to eventually replace ``-jobs=N`` and ``-workers=N`` with ``-fork=N``. 450 clang++ -fsanitize=address,fuzzer test_fuzzer.cc 589 `Clang Coverage <https://clang.llvm.org/docs/SourceBasedCodeCoverage.html>`_, 634 …/usr/lib/<llvm-version>/lib/clang/<clang-version>/lib/linux/libclang_rt.fuzzer_no_main-<architectu… [all …]
|
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 33 the HTML/XML requirement to replace ``<`` with ``<`` and the like. 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 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>`_.
|
H A D | GettingStarted.rst | 19 C-like languages use the `Clang <https://clang.llvm.org/>`_ front end. This 31 Getting Started <https://clang.llvm.org/get_started.html>`_ page might have more 65 subprojects you'd like to additionally build. Can include any of: clang, 66 clang-tools-extra, lldb, compiler-rt, lld, polly, or cross-project-tests. 69 ``-DLLVM_ENABLE_PROJECTS="clang" -DLLVM_ENABLE_RUNTIMES="libcxx;libcxxabi"``. 114 version of the clang or llvm libraries that is already present on your 166 clang clang, cmake CLANG_INCLUDE_TESTS=ON (Required for check-clang only) 170 Example for building stand-alone `clang`: 177 build_clang=`pwd`/build-clang 190 cmake -G Ninja -S $llvm/clang -B $build_clang \ [all …]
|
H A D | ExceptionHandling.rst | 12 exception handling in LLVM. It describes the format that LLVM exception 36 exception frame format can be found at `Exception Frames 252 a rethrow from within the catch may replace this call with a 371 a destination address by `llvm.eh.sjlj.longjmp`_. The buffer format and the 373 ``__builtin_setjmp`` implementation allowing code built with the clang and GCC 437 The format of this call frame information (CFI) is often platform-dependent, 438 however. ARM, for example, defines their own format. Apple has their own compact 439 unwind info format. On Windows, another format is used for all architectures 448 referred to as the language-specific data area (LSDA). The format of the LSDA 807 …but not in LLVM unwinder (`libunwind <https://clang.llvm.org/docs/Toolchain.html#unwind-library>`_… [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 210 variable from memory to SSA values will replace this call with possibly 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)… [all …]
|
/openbsd-src/gnu/llvm/clang/tools/scan-build-py/lib/libscanbuild/ |
H A D | report.py | 21 from libscanbuild.clang import get_version 88 | </head>""", indent).format(html_title=args.html_title)) 99 | </table>""", indent).format(html_title=args.html_title, 104 clang_version=get_version(args.clang), 143 | </tr>""", indent).format(bug_counter.total)) 148 | </tr>""", indent).format(category)) 160 | </tr>""", indent).format(**bug_type)) 206 | </tr>""", indent).format(**current)) 244 | </tr>""", indent).format(**current)) 273 lambda bug: '{bug_line}.{bug_path_length}:{bug_file}'.format(**bug)) [all …]
|
H A D | analyze.py | 36 from libscanbuild.clang import get_version, get_arguments, get_triple_arch, \ 223 'clang': args.clang, 288 'ANALYZE_BUILD_CLANG': args.clang if need_analyzer(args.build) else '', 390 result.append('-analyzer-constraints={0}'.format( 401 result.append('-analyzer-output={0}'.format(args.output_format)) 429 raise KeyError('{0} not passed to {1}'.format( 521 handle.write(error.title().replace('_', ' ') + os.linesep)
|
/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) 283 clang_dir = clang_dir.replace('\\', '/') 288 def get_clang_has_lsan(self, clang, triple): argument 289 if not clang: 295 clang_binary = clang.split()[0] 450 message = "couldn't find '{}' program".format(name) [all …]
|
/openbsd-src/gnu/llvm/libcxx/docs/ |
H A D | UsingLibcxx.rst | 29 $ clang++ -std=c++17 test.cpp 71 $ clang++ -stdlib=libc++ test.cpp 88 $ clang++ -nostdinc++ -nostdlib++ \ 138 If you would prefer to not use that flag, then you can replace ``/path/to/include-what-you-use/shar… 176 overriden at compile-time by defining the ``_LIBCPP_VERBOSE_ABORT(format, args...)`` variadic macro. 177 When that macro is defined, it will be called with a format string as the first argument, followed … 178 a series of arguments to format using printf-style formatting. Compile-time customization may be 191 void __libcpp_verbose_abort(char const* format, ...) 193 This mechanism is similar to how one can replace the default definition of ``operator new`` 201 void std::__libcpp_verbose_abort(char const* format, ...) { [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">, 526 def: Separate<["-"], "b">, Alias<format>, HelpText<"Alias for --format">; 592 def opt_remarks_format: Separate<["--"], "opt-remarks-format">, 593 HelpText<"The format used for serializing remarks (default: YAML)">; 615 def thinlto_object_suffix_replace_eq: JJ<"thinlto-object-suffix-replace=">; 616 def thinlto_prefix_replace_eq: JJ<"thinlto-prefix-replace=">; [all …]
|
/openbsd-src/gnu/llvm/lldb/docs/use/ |
H A D | extensions.rst | 11 modules <https://clang.llvm.org/docs/Modules.html>`_ more efficiently. 29 (``.o``) files and replace them with forward declarations to save 118 files. The ``dsymutil`` debug info linker also understands this format
|
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/llvm/docs/HistoricalNotes/ |
H A D | 2007-OriginalClangReadme.txt | 8 clang: noun 70 clang - An example driver, client of the libraries at various levels. 74 easy to reuse individual parts or replace pieces if desired. For example, to 92 II. Usage of clang driver: 95 - Help: clang --help 127 For more information on getting Graphviz to work with clang/LLVM, 136 * Full diagnostic customization by client (can format diagnostics however they
|
/openbsd-src/gnu/llvm/clang/docs/ |
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 | InternalsManual.rst | 80 ``clang/Basic/Diagnostic*Kinds.td`` files, depending on what library will be 82 diagnostic, the severity of the diagnostic and the English translation + format 129 The format string for the diagnostic is very simple, but it has some power. It 132 some simple format strings: 137 "format string contains '\\0' within the string body" 143 These examples show some important points of format strings. You can use any 156 order as they are specified, you could have a format string with "``%1 %0``" 161 Here are some "best practices" for writing the English format string: 182 including variable names, types, labels, etc. The "``select``" format can be 195 It is really easy to add format specifiers to the Clang diagnostics system, but [all …]
|
/openbsd-src/gnu/llvm/llvm/docs/Proposals/ |
H A D | GitHubMove.rst | 85 projects. Any of these could replace the code-hosting infrastructure that we 129 We can thus use this revision number to ensure that e.g. `clang -v` reports a 155 email format unchanged besides the commit URL. 253 # Configure LLVM and clang 254 cmake path/to/monorepo -DLLVM_ENABLE_PROJECTS=clang 341 At this point you have every sub-project (llvm, clang, lld, lldb, ...), which 377 Let's look how to assemble llvm+clang+libcxx at a given revision. 386 svn co https://llvm.org/svn/llvm-project/clang/trunk clang -r $REVISION 399 git clone https://llvm.org/git/clang.git 400 cd clang/ [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 475 class [[clang::sycl_special_class]] accessor {}; [all …]
|
/openbsd-src/usr.sbin/nsd/ |
H A D | acx_nlnetlabs.m4 | 26 # 2015-12-11 FLTO check for new OSX, clang. 73 # ACX_CHECK_FORMAT_ATTRIBUTE - find cc printf format syntax. 94 # AHX_CONFIG_FORMAT_ATTRIBUTE - config.h text for format. 119 # AHX_MEMCMP_BROKEN - replace memcmp func for CHECK_MEMCMP_SIGNED. 438 dnl in a way that supports clang and suncc (that flag does something else, 458 dnl Check the printf-format attribute (if any) 463 AC_MSG_CHECKING(whether the C compiler (${CC-cc}) accepts the "format" attribute) 467 void f (char *format, ...) __attribute__ ((format (printf, 1, 2))); 468 void (*pf) (char *format, ...) __attribute__ ((format (printf, 1, 2))); 476 AC_DEFINE(HAVE_ATTR_FORMAT, 1, [Whether the C compiler accepts the "format" attribute]) [all …]
|
/openbsd-src/usr.sbin/unbound/ |
H A D | acx_nlnetlabs.m4 | 26 # 2015-12-11 FLTO check for new OSX, clang. 73 # ACX_CHECK_FORMAT_ATTRIBUTE - find cc printf format syntax. 94 # AHX_CONFIG_FORMAT_ATTRIBUTE - config.h text for format. 119 # AHX_MEMCMP_BROKEN - replace memcmp func for CHECK_MEMCMP_SIGNED. 438 dnl in a way that supports clang and suncc (that flag does something else, 458 dnl Check the printf-format attribute (if any) 463 AC_MSG_CHECKING(whether the C compiler (${CC-cc}) accepts the "format" attribute) 467 void f (char *format, ...) __attribute__ ((format (printf, 1, 2))); 468 void (*pf) (char *format, ...) __attribute__ ((format (printf, 1, 2))); 476 AC_DEFINE(HAVE_ATTR_FORMAT, 1, [Whether the C compiler accepts the "format" attribute]) [all …]
|
/openbsd-src/gnu/llvm/clang/lib/Driver/ |
H A D | Driver.cpp | 106 using namespace clang::driver; 107 using namespace clang; 782 Diag(clang::diag::err_drv_mix_cuda_hip); in CreateOffloadingDeviceToolChains() 804 Diag(clang::diag::err_drv_unsupported_opt_for_language_mode) in CreateOffloadingDeviceToolChains() 835 Diag(clang::diag::err_drv_expecting_fopenmp_with_fopenmp_targets); in CreateOffloadingDeviceToolChains() 849 Diag(clang::diag::warn_drv_empty_joined_argument) in CreateOffloadingDeviceToolChains() 895 Diag(clang::diag::err_drv_failed_to_deduce_target_from_arch) << Arch; in CreateOffloadingDeviceToolChains() 902 Diag(clang::diag::err_drv_failed_to_deduce_target_from_arch) in CreateOffloadingDeviceToolChains() 918 Diag(clang::diag::warn_drv_omp_offload_target_duplicate) in CreateOffloadingDeviceToolChains() 929 Diag(clang::diag::err_drv_invalid_omp_target) << Val; in CreateOffloadingDeviceToolChains() [all …]
|
/openbsd-src/gnu/llvm/llvm/cmake/ |
H A D | config-ix.cmake | 245 …message(STATUS "The xar file format has been deprecated: LLVM_HAVE_LIBXAR might be removed in the … 246 # The xar file format has been deprecated since macOS 12.0. 503 # If build targets includes "host" or "Native", then replace with native architecture. 539 # Allow setting clang-cl's /winsysroot flag. 541 "If set, argument to clang-cl's /winsysroot")
|