Magic-Mirror/llvm-capstone
1
0
Fork 0
mirror of https://github.com/capstone-engine/llvm-capstone.git synced 2024-11-25 14:50:26 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Documentation: formatting fixes

Browse Source 
llvm-svn: 176948
This commit is contained in:
Dmitri Gribenko 2013-03-13 14:26:35 +00:00
parent 2325273641
commit 3605f319dd
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
clang/docs/AutomaticReferenceCounting.rst
View File

@ -1347,7 +1347,7 @@ object pointer. The corresponding actual sequence executed is the
However, under certain circumstances, ARC is permitted to re-order and
eliminate operations in a manner which may alter the overall
computation history beyond what is permitted by the general "as if"
rule of C/C++ and the :ref:`restrictions <_arc.objects.retains>` on
rule of C/C++ and the :ref:`restrictions <arc.objects.retains>` on
the implementation of ``retain`` and ``release``.
.. admonition:: Rationale
@ -1359,6 +1359,7 @@ the implementation of ``retain`` and ``release``.
example, consider the following code:
.. code-block:: objc
id x = _ivar;
[x foo];
@ -1450,7 +1451,7 @@ dependency is not carried by values that are stored to objects.
itself cause dependence, but since generally the optimizer will not
be able to prove that the function doesn't depend on that parameter,
it will be forced to conservatively assume it does.
Dependency propagates to values loaded from a pointer because those
values might be invalidated by deallocating the object. For
example, given the code ``__strong id x = p->ivar;``, ARC must not