Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

These macros copy and encode data values from any CPU memory address to any other memory address.

Files

lib_mem.h

Prototypes

Arguments

addr_dest

Lowest CPU memory address to copy/encode source address’s data value.

addr_src

Lowest CPU memory address of the data value to copy/encode.

val_size

Number of data value octets to copy/encode.

Returned Value

None.

Required Configuration

None.

Notes / Warnings

CPU memory addresses/pointers not checked for NULL nor overlapping memory addresses which may result in undefined copy behavior.

Copy/encode data values based on the values’ data-word order in CPU memory:

MEM_VAL_COPY_SET_xxx_BIG()

Encode big-endian data values — data words’ most significant octet at lowest memory address

MEM_VAL_COPY_SET_xxx_LITTLE()

Encode little-endian data values — data words’ least significant octet at lowest memory address

MEM_VAL_COPY_SET_xxx()

Encode data values using CPU’s native or configured data-word order

MEM_VAL_COPY_SET_xxx() macros copy/encode data values without regard to CPU word-aligned addresses. Thus for processors that require data word alignment, data words can be copied/encoded to/from any CPU addresses, word-aligned or not, without generating data-word-alignment exceptions/faults.

MEM_VAL_COPY_SET_xxx() macros are more efficient than MEM_VAL_SET_xxx() macros and are also fully independent of CPU data-word-alignment and should be used whenever possible. Fixed-size copy MEM_VAL_COPY_SET_INTxxU_xxx() macros are more efficient than dynamic-size copy MEM_VAL_COPY_SET_INTU_xxx() macros and should be used whenever possible.

MEM_VAL_COPY_SET_xxx() macros are not atomic operations and must not be used on any non-static (i.e., volatile) variables, registers, hardware, etc.; without the caller of the macros providing some form of additional protection (e.g. mutual exclusion).

Since octet-order copy/conversion are inverse operations, MEM_VAL_COPY_GET_xxx() and MEM_VAL_COPY_SET_xxx() memory data-copy get/set macros are inverse, but identical, operations and are provided in both forms for semantics and consistency.

Example Usage

  • No labels