Dear Kevin,
On 08/29/17 20:55, Kevin O'Connor wrote:
Signed-off-by: Kevin O'Connor kevin@koconnor.net
docs/Memory_Model.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/Memory_Model.md b/docs/Memory_Model.md index 0668bd8..1ebe865 100644 --- a/docs/Memory_Model.md +++ b/docs/Memory_Model.md @@ -192,7 +192,7 @@ There are three low-level memory access macros:
- GET_FARVAR / SET_FARVAR : Assigns the extra segment (%es) to the given segment id and then performs the given memory access via %es.
-* GET_FLATVAR / SET_FLATVAR : These macros take a 32bit pointer, +* GET_FLATPTR / SET_FLATPTR : These macros take a 32bit pointer, construct a segment/offset pair valid in real mode, and then perform the given access. These macros must not be used in 16bit protected mode or 32bit segmented mode. @@ -209,11 +209,11 @@ macros are also available.
- GET_LOW / SET_LOW : Access internal variables marked with VARLOW. (There are also related macros GET_LOWFLAT / SET_LOWFLAT for
- accessing storage allocated with malloc_low).
accessing storage allocated with malloc_low.)
- GET_GLOBAL : Access internal variables marked with the VAR16 or
VARFSEG flags. (There is also the related macro GET_GLOBALFLAT for
- accessing storage allocated with malloc_fseg).
accessing storage allocated with malloc_fseg.)
Memory available during initialization
Reviewed-by: Paul Menzel pmenzel@molgen.mpg.de
Kind regards,
Paul