fix some typos to cycle bots
This commit is contained in:
parent
102814b4d3
commit
b50431defb
|
@ -63,7 +63,7 @@ The following flags bits are in use thusly for a possible ABI.2010.3.16:
|
|||
enum {
|
||||
// Set to true on blocks that have captures (and thus are not true
|
||||
// global blocks) but are known not to escape for various other
|
||||
// reasons. For backward compatiblity with old runtimes, whenever
|
||||
// reasons. For backward compatibility with old runtimes, whenever
|
||||
// BLOCK_IS_NOESCAPE is set, BLOCK_IS_GLOBAL is set too. Copying a
|
||||
// non-escaping block returns the original block and releasing such a
|
||||
// block is a no-op, which is exactly how global blocks are handled.
|
||||
|
|
|
@ -2145,7 +2145,7 @@ Checked Arithmetic Builtins
|
|||
---------------------------
|
||||
|
||||
Clang provides a set of builtins that implement checked arithmetic for security
|
||||
critical applications in a manner that is fast and easily expressable in C. As
|
||||
critical applications in a manner that is fast and easily expressible in C. As
|
||||
an example of their usage:
|
||||
|
||||
.. code-block:: c
|
||||
|
@ -2538,7 +2538,7 @@ pointers and integers.
|
|||
These builtins can be used to avoid relying on implementation-defined behavior
|
||||
of arithmetic on integers derived from pointers.
|
||||
Additionally, these builtins retain type information and, unlike bitwise
|
||||
arithmentic, they can perform semantic checking on the alignment value.
|
||||
arithmetic, they can perform semantic checking on the alignment value.
|
||||
|
||||
**Syntax**:
|
||||
|
||||
|
|
|
@ -107,14 +107,14 @@ relies on padding and the ability to map a file over the existing memory
|
|||
mapping which is generally only available on POSIX systems and isn't suitable
|
||||
for other platforms.
|
||||
|
||||
On Fuchsia, we rely on the the ability to relocate counters at runtime using a
|
||||
On Fuchsia, we rely on the ability to relocate counters at runtime using a
|
||||
level of indirection. On every counter access, we add a bias to the counter
|
||||
address. This bias is stored in ``__llvm_profile_counter_bias`` symbol that's
|
||||
provided by the profile runtime and is initially set to zero, meaning no
|
||||
relocation. The runtime can map the profile into memory at abitrary location,
|
||||
relocation. The runtime can map the profile into memory at arbitrary locations,
|
||||
and set bias to the offset between the original and the new counter location,
|
||||
at which point every subsequent counter access will be to the new location,
|
||||
which allows updating profile directly akin to the continous mode.
|
||||
which allows updating profile directly akin to the continuous mode.
|
||||
|
||||
The advantage of this approach is that doesn't require any special OS support.
|
||||
The disadvantage is the extra overhead due to additional instructions required
|
||||
|
|
Loading…
Reference in New Issue