mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-18 11:50:38 -08:00
Fixing basic restructuredtext syntax and reference errors found by tool/checkrst.
This commit is contained in:
parent
e994fe3f57
commit
446ba2afcc
5 changed files with 7 additions and 10 deletions
|
|
@ -246,7 +246,7 @@ segment sizes are rounded up to the arena grain size.
|
|||
|
||||
_`.fun.awlsegcreate.where`: The segment is allocated using a
|
||||
generation preference, using the generation number stored in the
|
||||
``AWLStruct`` (the ``gen`` field), see `.poolstruct.gen`_ above.
|
||||
``AWLStruct`` (the ``gen`` field), see `.poolstruct`_ above.
|
||||
|
||||
``Res awlSegInit(Seg seg, Pool pool, Addr base, Size size, ArgList args)``
|
||||
|
||||
|
|
|
|||
|
|
@ -88,12 +88,9 @@ okay), the protection is set to ``PROT_READ|PROT_WRITE|PROT_EXEC``.
|
|||
.. _design.mps.prot.if.set: prot#.if.set
|
||||
|
||||
_`.fun.set.assume.mprotect`: We assume that the call to ``mprotect()``
|
||||
always succeeds.
|
||||
|
||||
_`.fun.set.assume.mprotect`: This is because we should always call the
|
||||
function with valid arguments (aligned, references to mapped pages,
|
||||
and with an access that is compatible with the access of the
|
||||
underlying object).
|
||||
always succeeds. We should always call the function with valid
|
||||
arguments (aligned, references to mapped pages, and with an access
|
||||
that is compatible with the access of the underlying object).
|
||||
|
||||
_`.fun.sync`: ``ProtSync()`` does nothing in this implementation as
|
||||
``ProtSet()`` sets the protection without any delay.
|
||||
|
|
|
|||
|
|
@ -569,7 +569,7 @@ following:
|
|||
A function called by ``SomeClassGet()``. All the class
|
||||
initialization code is actually in this function.
|
||||
|
||||
_`.impl.subclass`: The subclass test `.if.subclass`_ is implemented
|
||||
_`.impl.subclass`: The subclass test `.if.is-subclass`_ is implemented
|
||||
using an array of superclasses [Cohen_1991]_ giving a fast
|
||||
constant-time test. (RB_ tried an approach using prime factors
|
||||
[Gibbs_2004]_ but found that they overflowed in 32-bits too easily to
|
||||
|
|
|
|||
|
|
@ -257,7 +257,7 @@ _`.proof.sync`: As the depth of a segment cannot be negative
|
|||
| ⇒ all segments are synced (by `.inv.unsynced.depth`_)
|
||||
|
||||
_`.proof.access`: If the mutator is running then all segments must be
|
||||
synced (`.inv.unsynced.suspend`_). Which means that the hardware
|
||||
synced (`.inv.unsynced.suspended`_). Which means that the hardware
|
||||
protection (protection mode) must reflect the software protection
|
||||
(shield mode). Hence all shielded memory will be hardware protected
|
||||
while the mutator is running. This ensures `.prop.mutator.access`_.
|
||||
|
|
|
|||
|
|
@ -280,7 +280,7 @@ B. Document History
|
|||
.. _NB: mailto:nb@ravenbrook.com
|
||||
.. _RHSK: mailto:rhsk@ravenbrook.com
|
||||
.. _GDR: mailto:gdr@ravenbrook.com
|
||||
.. _PNJ mailto:pnj@ravenbrook.com
|
||||
.. _PNJ: mailto:pnj@ravenbrook.com
|
||||
|
||||
C. Copyright and License
|
||||
------------------------
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue