RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-12-12 14:06:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Make formatting more consistent and tidy-up.

Browse Source 
llvm-svn: 179689
This commit is contained in:
Eli Bendersky 2013-04-17 17:17:20 +00:00
parent cd0483fb18
commit 882aaffcf6
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/LangRef.rst
View File

@ -4618,10 +4618,10 @@ The '``store``' instruction is used to write to memory.
Arguments: Arguments:
"""""""""" """"""""""
There are two arguments to the '``store``' instruction: a value to store There are two arguments to the ``store`` instruction: a value to store
and an address at which to store it. The type of the '``<pointer>``' and an address at which to store it. The type of the ``<pointer>``
operand must be a pointer to the :ref:`first class <t_firstclass>` type of operand must be a pointer to the :ref:`first class <t_firstclass>` type of
the '``<value>``' operand. If the ``store`` is marked as ``volatile``, the ``<value>`` operand. If the ``store`` is marked as ``volatile``,
then the optimizer is not allowed to modify the number or order of then the optimizer is not allowed to modify the number or order of
execution of this ``store`` with other :ref:`volatile execution of this ``store`` with other :ref:`volatile
operations <volatile>`. operations <volatile>`.
@ -4638,18 +4638,18 @@ has undefined behavior if the alignment is not set to a value which is
at least the size in bytes of the pointee. ``!nontemporal`` does not at least the size in bytes of the pointee. ``!nontemporal`` does not
have any defined semantics for atomic stores. have any defined semantics for atomic stores.
The optional constant "align" argument specifies the alignment of the The optional constant ``align`` argument specifies the alignment of the
operation (that is, the alignment of the memory address). A value of 0 operation (that is, the alignment of the memory address). A value of 0
or an omitted "align" argument means that the operation has the abi or an omitted ``align`` argument means that the operation has the ABI
alignment for the target. It is the responsibility of the code emitter alignment for the target. It is the responsibility of the code emitter
to ensure that the alignment information is correct. Overestimating the to ensure that the alignment information is correct. Overestimating the
alignment results in an undefined behavior. Underestimating the alignment results in undefined behavior. Underestimating the
alignment may produce less efficient code. An alignment of 1 is always alignment may produce less efficient code. An alignment of 1 is always
safe. safe.
The optional !nontemporal metadata must reference a single metatadata The optional ``!nontemporal`` metadata must reference a single metatadata
name <index> corresponding to a metadata node with one i32 entry of name ``<index>`` corresponding to a metadata node with one ``i32`` entry of
value 1. The existence of the !nontemporal metatadata on the instruction value 1. The existence of the ``!nontemporal`` metatadata on the instruction
tells the optimizer and code generator that this load is not expected to tells the optimizer and code generator that this load is not expected to
be reused in the cache. The code generator may select special be reused in the cache. The code generator may select special
instructions to save cache bandwidth, such as the MOVNT instruction on instructions to save cache bandwidth, such as the MOVNT instruction on
@ -4658,8 +4658,8 @@ x86.
Semantics: Semantics:
"""""""""" """"""""""
The contents of memory are updated to contain '``<value>``' at the The contents of memory are updated to contain ``<value>`` at the
location specified by the '``<pointer>``' operand. If '``<value>``' is location specified by the ``<pointer>`` operand. If ``<value>`` is
of scalar type then the number of bytes written does not exceed the of scalar type then the number of bytes written does not exceed the
minimum number of bytes needed to hold all bits of the type. For minimum number of bytes needed to hold all bits of the type. For
example, storing an ``i24`` writes at most three bytes. When writing a example, storing an ``i24`` writes at most three bytes. When writing a