Home
last modified time | relevance | path

Searched +refs:clang +refs:format +refs:buffer (Results 1 – 25 of 52) sorted by relevance

123

/openbsd-src/gnu/llvm/clang/docs/
H A DClangFormat.rst13 :program:`clang-format` is located in `clang/tools/clang-format` and can be used
14 to format C/C++/Java/JavaScript/JSON/Objective-C/Protobuf/C# code.
20 $ clang-format --help
21 OVERVIEW: A tool to format C/C++/Java/JavaScript/JSON/Objective-C/Protobuf/C# code.
29 USAGE: clang-format [options] [@<file>] [<file> ...]
33 Clang-format options:
37 =unknown - If set, unknown format options are only warned about.
41 differing format depending on an option being
44 .clang-format file.
46 If this is not passed, the .clang-format file is searched
[all …]
H A DClangOffloadPackager.rst14 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
158 USAGE: clang-offload-packager [options]
168 clang-offload-packager options:
[all …]
H A DClangFormatStyleOptions.rst4 in this file directly. Instead, modify them in include/clang/Format/Format.h
22 When using :program:`clang-format` command line utility or
23 ``clang::format::reformat(...)`` functions from code, one can either use one of
28 Configuring Style with clang-format
31 :program:`clang-format` supports two ways to provide custom style options:
33 use ``-style=file`` and put style configuration in the ``.clang-format`` or
34 ``_clang-format`` file in the project directory.
36 When using ``-style=file``, :program:`clang-format` for each input file will
37 try to find the ``.clang-format`` file located in the closest parent directory
41 When using ``-style=file:<format_file_path>``, :program:`clang-format` for
[all …]
H A DPCHInternals.rst12 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 DSourceBasedCodeCoverage.rst11 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…
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.
359 described above, use the following to save the profile directly to a buffer
364 buffer of this size.
[all …]
H A DUsersManual.rst18 `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 DInternalsManual.rst80 ``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 …]
H A DLanguageExtensions.rst50 #define __has_builtin(x) 0 // Compatibility with non-clang compilers.
81 #define __has_constexpr_builtin(x) 0 // Compatibility with non-clang compilers.
114 #define __has_feature(x) 0 // Compatibility with non-clang compilers.
174 #if __has_cpp_attribute(clang::fallthrough)
175 #define FALLTHROUGH [[clang::fallthrough]]
181 The attribute scope tokens ``clang`` and ``_Clang`` are interchangeable, as are
199 #define __has_c_attribute(x) 0 // Compatibility with non-clang compilers.
210 The attribute scope tokens ``clang`` and ``_Clang`` are interchangeable, as are
226 #define __has_attribute(x) 0 // Compatibility with non-clang compilers.
253 #define __has_declspec_attribute(x) 0 // Compatibility with non-clang compilers.
[all …]
H A DModules.rst99 … the full complexity of the language. Maintaining a stable binary module format across architectur…
288 …e updated to take into account the default options passed to ``clang -cc1``. (See ``clang use.c -v…
289 …-file=`` or ``-fimplicit-module-maps`` options explicitly. When using the clang driver, ``-fimplic…
296 clang -cc1 -emit-module -o prebuilt/A.pcm -fmodules module.modulemap -fmodule-name=A
297 …clang -cc1 -emit-module -o prebuilt/B.pcm -fmodules module.modulemap -fmodule-name=B -fmodule-file…
298 …clang -cc1 -emit-obj use.c -fmodules -fmodule-map-file=module.modulemap -fmodule-file=A=prebuilt/A…
305 clang -cc1 -emit-module -o prebuilt/A.pcm -fmodules module.modulemap -fmodule-name=A
306 …clang -cc1 -emit-module -o prebuilt/B.pcm -fmodules module.modulemap -fmodule-name=B -fprebuilt-mo…
307 clang -cc1 -emit-obj use.c -fmodules -fimplicit-module-maps -fprebuilt-module-path=prebuilt
314 …clang -cc1 -emit-obj use.c -fmodules -fimplicit-module-maps -fmodules-cache-path=prebuilt -fdisabl…
[all …]
/openbsd-src/gnu/llvm/llvm/docs/
H A DCFIVerify.rst30 - 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
65 the disassembly. A control flow graph would be generated from a small buffer of
H A DExceptionHandling.rst12 exception handling in LLVM. It describes the format that LLVM exception
36 exception frame format can be found at `Exception Frames
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
376 The single parameter is a pointer to a five word buffer in which the calling
393 a buffer populated by `llvm.eh.sjlj.setjmp`_. The frame pointer and stack
394 pointer are restored from the buffer, then control is transferred to the
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
[all …]
H A DSourceLevelDebugging.rst12 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
201 %buffer = alloca [256 x i8], align 8
202 ; The address of i is buffer+64.
203 call void @llvm.dbg.addr(metadata [256 x i8]* %buffer, metadata !3,
299 In order to handle this, the LLVM debug format uses the metadata attached to
[all …]
H A DJITLink.rst21 object format; including static initializers, exception handling, thread local
24 (e.g. C++ requires object format support for static initializers to support
27 many features). For some object format features support is provided entirely
37 2. Support for all object format features.
191 or subsections, depending on the format), and annotations describing how to
761 for advanced JIT features, including object format features that require
765 ORC Runtime support for object format features typically requires cooperation
786 ``LinkGraph`` from an in-memory buffer containing an object file. This is how
790 both the object format and architecture are known ahead of time.
792 #. ``createLinkGraph_<Object-Format>`` can be used when the object format is
[all …]
/openbsd-src/gnu/llvm/clang/docs/CommandGuide/
H A Dclang.rst1 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
63 the same driver. Please see <https://clang-analyzer.llvm.org> for more details
437 option transparently switches the Clang module format to object file
502 assembly files, otherwise this generates LLVM bitcode format object files
627 Adds an implicit #define into the predefines buffer which is read before the
632 Adds an implicit #undef into the predefines buffer which is read before the
637 Adds an implicit #include into the predefines buffer which is read before the
[all …]
/openbsd-src/gnu/llvm/clang/include/clang/Basic/
H A DDiagnosticGroups.td20 // Empty DiagGroups are recognized by clang but ignored.
275 def FormatInsufficientArgs : DiagGroup<"format-insufficient-args">;
276 def FormatExtraArgs : DiagGroup<"format-extra-args">;
277 def FormatZeroLength : DiagGroup<"format-zero-length">;
485 def : DiagGroup<"missing-format-attribute">;
713 def ObjCCStringFormat : DiagGroup<"cstring-format-directive">;
738 // (#pragma clang optimize, noinline) so suggest nothing for now.
743 def PragmaClangAttribute : DiagGroup<"pragma-clang-attribute">;
830 def VectorConversion : DiagGroup<"vector-conversion">; // clang specific
940 def FormatInvalidSpecifier : DiagGroup<"format-invalid-specifier">;
[all …]
H A DAttrDocs.td9 // 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
387 buffer<int, 1> a(range<1>{1024});
[all …]
/openbsd-src/gnu/llvm/lldb/source/Plugins/LanguageRuntime/ObjC/AppleObjCRuntime/
H A DAppleObjCRuntimeV2.cpp1241 std::string buffer("OBJC_IVAR_$_"); in GetByteOffsetForIvar() local
1242 buffer.append(class_name.AsCString()); in GetByteOffsetForIvar()
1243 buffer.push_back('.'); in GetByteOffsetForIvar()
1244 buffer.append(ivar_name); in GetByteOffsetForIvar()
1245 ConstString ivar_const_str(buffer.c_str()); in GetByteOffsetForIvar()
1744 [[clang::fallthrough]]; in ComputeHelper()
1748 [[clang::fallthrough]]; in ComputeHelper()
1752 [[clang::fallthrough]]; in ComputeHelper()
1792 << llvm::format(g_shared_cache_class_name_funcptr, in GetClassInfoUtilityFunctionImpl()
2024 DataBufferHeap buffer(num_class_infos * class_info_byte_size, 0); in UpdateISAToDescriptorMap() local
[all …]
/openbsd-src/usr.sbin/nsd/doc/
H A DChangeLog165 - Fix unused variable warning in unit test, from clang compile.
263 - Update to clang 14 in cirrus build test on Ubuntu Jammy 22.04.
309 readable text format. The number of IXFRs is num.rixfr in
664 - Fix missing parenthesis on size of fix to init buffer.
670 - Fix #133: fix 0-init of local ( stack ) buffer.
751 - Retry when udp send buffer is full to wait until buffer space is
1034 - Fixup clang analysis warning in xfrd_parse_received_xfr_packet
1128 - PR #12: send-buffer-size, receive-buffer-size,
1187 - Nicer output on travis for clang analysis.
1197 - Fix to avoid buffer alloc with global buffer in tls write handler.
[all …]
H A DRELNOTES138 - Fix unused variable warning in unit test, from clang compile.
181 readable text format. The number of IXFRs is num.rixfr in
349 - Fix #133: fix 0-init of local ( stack ) buffer.
350 - Fix missing parenthesis on size of fix to init buffer.
415 - Retry when udp send buffer is full to wait until buffer space is
552 - Fixup clang analysis warning in xfrd_parse_received_xfr_packet
597 - PR #12: send-buffer-size, receive-buffer-size,
636 - Use travis for build check, initial unit test and clang analysis.
646 - Fix to avoid buffer alloc with global buffer in tls write handler.
720 - please clang analyzer and fix parse of IPSECKEY with bad gateway.
[all …]
/openbsd-src/gnu/llvm/llvm/docs/CommandGuide/
H A Dllvm-mca.rst30 For example, you can compile code with clang, output assembly, and pipe it
35 $ clang foo.c -O2 -target x86_64-unknown-unknown -S -o - | llvm-mca -mcpu=btver2
41 …$ clang foo.c -O2 -target x86_64-unknown-unknown -mllvm -x86-asm-syntax=intel -S -o - | llvm-mca -…
96 the AT&T (vic. Intel) assembly format for the code printed out by the tool in
101 Prefer hex format for numeric literals in the output assembly printed as part
217 Print the requested views in valid JSON format. The instructions and the
321 The `Clang options to emit optimization reports <https://clang.llvm.org/docs/UsersManual.html#optio…
770 counters for the dispatch logic, the reorder buffer, the retire control unit,
803 [2] Average number of used buffer entries.
804 [3] Maximum number of used buffer entries.
[all …]
/openbsd-src/gnu/llvm/llvm/tools/llvm-objdump/
H A DMachODump.cpp207 #pragma clang diagnostic push in ScopedXarFile()
208 #pragma clang diagnostic ignored "-Wdeprecated-declarations" in ScopedXarFile()
210 #pragma clang diagnostic pop in ScopedXarFile()
284 outs() << "\t.byte " << format("%3u", Value) << "\t@ KIND_JUMP_TABLE8\n"; in DumpDataInCode()
291 outs() << "\t.short " << format("%5u", Value & 0xffff) in DumpDataInCode()
405 Fmt << format("0x%x", Val); in printRelocationTargetName()
415 Fmt << format("0x%0" PRIx64, Val); in printRelocationTargetName()
649 outs() << format("0x%016" PRIx64, addr + j * stride) << " "; in PrintIndirectSymbolTable()
651 outs() << format("0x%08" PRIx32, (uint32_t)addr + j * stride) << " "; in PrintIndirectSymbolTable()
667 outs() << format("%5u ", indirect_symbol); in PrintIndirectSymbolTable()
[all …]
/openbsd-src/gnu/llvm/clang/docs/tools/
H A Dclang-formatted-files.txt113 clang/bindings/python/tests/cindex/INPUTS/header1.h
114 clang/bindings/python/tests/cindex/INPUTS/header2.h
115 clang/bindings/python/tests/cindex/INPUTS/header3.h
116 clang/examples/Attribute/Attribute.cpp
117 clang/examples/CallSuperAttribute/CallSuperAttrInfo.cpp
118 clang/examples/PluginsOrder/PluginsOrder.cpp
119 clang/include/clang/Analysis/BodyFarm.h
120 clang/include/clang/Analysis/IssueHash.h
121 clang/include/clang/Analysis/MacroExpansionContext.h
122 clang/include/clang/Analysis/Analyses/CalledOnceCheck.h
[all …]
/openbsd-src/gnu/llvm/clang/docs/analyzer/
H A Dcheckers.rst75 <https://clang.llvm.org/docs/LanguageExtensions.html#memory-references-to-specified-segments>`__
292 const char *c = s.data(); // note: pointer to inner buffer of 'std::string' obtained here
293 s = "clang"; // note: inner buffer of 'std::string' reallocated by call to 'operator='
299 // note: pointer to inner buffer of 'std::string' obtained here
300 // note: inner buffer of 'std::string' deallocated by call to destructor
798 Warn when 'mkstemp' is passed fewer than 6 X's in the format string.
863 …Warn on occurrences of unsafe or deprecated buffer handling functions, which now have a secure var…
963 // warn: potential buffer overflow
2109 Warn about buffer overflows (older checker).
2147 Warn about buffer overflows (newer checker).
[all …]
/openbsd-src/lib/libz/
H A DChangeLog9 - Fix bug in inflateSync() for data held in bit buffer
21 - Fix bug when using gzflush() with a very small buffer
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
190 - Check for input buffer malloc failure in examples/gzappend.c
248 - Recognize clang as gcc
558 - Avoid buffer overrun in contrib/masmx64/gvmat64.asm [Simpson]
679 - Allow negative bits in inflatePrime() to delete existing bit buffer
796 - Add error return to gzread() for format or i/o error [Levin]
[all …]
/openbsd-src/lib/libexpat/
H A DChanges48 #914 Fix signedness of format strings
160 #818 CI: Adapt to breaking changes in clang-format
193 #771 #788 Improve buffer growth in XML_GetBuffer and XML_Parse
195 #759 #770 xmlwf: Support custom buffer size for XML_GetBuffer and read
231 #798 #800 Address clang-tidy warnings
238 #766 docs: Improve parse buffer variables in-code documentation
255 #798 CI: Enforce clang-tidy clean code
362 #637 apply-clang-format
[all...]

123