mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-10-07 10:54:01 +00:00
Fix typos in documentation
This commit is contained in:
parent
667a195fcd
commit
32870da3ba
@ -196,7 +196,7 @@ Changes in existing checks
|
||||
|
||||
- Improved :doc:`misc-include-cleaner
|
||||
<clang-tidy/checks/misc/include-cleaner>` check by adding option
|
||||
`DeduplicateFindings` to output one finding per symbol occurence.
|
||||
`DeduplicateFindings` to output one finding per symbol occurrence.
|
||||
|
||||
- Improved :doc:`modernize-loop-convert
|
||||
<clang-tidy/checks/modernize/loop-convert>` to support for-loops with
|
||||
|
@ -81,7 +81,7 @@ If the call is deemed suitable for conversion then:
|
||||
is of ``signed char`` or ``unsigned char`` type are wrapped in a
|
||||
``reinterpret_cast<const char *>``.
|
||||
- any arguments where the format string and the parameter differ in
|
||||
signedness will be wrapped in an approprate ``static_cast`` if `StrictMode`
|
||||
signedness will be wrapped in an appropriate ``static_cast`` if `StrictMode`
|
||||
is enabled.
|
||||
- any arguments that end in a call to ``std::string::c_str()`` or
|
||||
``std::string::data()`` will have that call removed.
|
||||
|
@ -2499,7 +2499,7 @@ and add the `csa_mark_sanitized` function.
|
||||
|
||||
Then calling `csa_mark_sanitized(X)` will tell the analyzer that `X` is safe to
|
||||
be used after this point, because its contents are verified. It is the
|
||||
responisibility of the programmer to ensure that this verification was indeed
|
||||
responsibility of the programmer to ensure that this verification was indeed
|
||||
correct. Please note that `csa_mark_sanitized` function is only declared and
|
||||
used during Clang Static Analysis and skipped in (production) builds.
|
||||
|
||||
|
@ -13,7 +13,7 @@ a list of open projects that one can start with:
|
||||
`LLVM style <https://llvm.org/docs/CodingStandards.html>`_ but differs in a
|
||||
few aspects: We use ``snake_case`` for non-constant variable and function
|
||||
names,``CamelCase`` for internal type names (those which are not defined in a
|
||||
public header), and ``CAPITILIZED_SNAKE_CASE`` for constants. When we started
|
||||
public header), and ``CAPITALIZED_SNAKE_CASE`` for constants. When we started
|
||||
working on the project, we started using the general LLVM style for
|
||||
everything. However, for a short period, we switched to the style that is
|
||||
currently followed by the `LLD project <https://github.com/llvm/llvm-project/tree/main/lld>`_.
|
||||
|
@ -7,7 +7,7 @@ Modules in libc++
|
||||
.. warning:: Modules are an experimental feature. It has additional build
|
||||
requirements and not all libc++ configurations are supported yet.
|
||||
|
||||
The work is still in an early developement state and not
|
||||
The work is still in an early development state and not
|
||||
considered stable nor complete
|
||||
|
||||
This page contains information regarding C++23 module support in libc++.
|
||||
|
@ -268,7 +268,7 @@ OPTIONS
|
||||
``#<number>[.<inline>] <address> <function> <file>:<line>:<col> (<module>+<relative address>)``
|
||||
|
||||
``<inline>`` provides frame numbers for calls inlined into the caller
|
||||
coresponding to ``<number>``. The inlined call numbers start at 1 and increase
|
||||
corresponding to ``<number>``. The inlined call numbers start at 1 and increase
|
||||
from callee to caller.
|
||||
|
||||
``<address>`` is an address inside the call instruction to the function. The
|
||||
|
@ -67,7 +67,7 @@ extending support to other linkers isn't planned for now.
|
||||
.. NOTE
|
||||
For standard linking the fat object files should be usable by any
|
||||
linker capable of using ELF objects, since the ``.llvm.lto`` section is
|
||||
marked ``SHF_EXLUDE``.
|
||||
marked ``SHF_EXCLUDE``.
|
||||
|
||||
Supported File Formats
|
||||
----------------------
|
||||
|
Loading…
Reference in New Issue
Block a user