Lines Matching refs:memory

5 when it comes to memory access. This document presents some details about
13 Unaligned memory accesses occur when you try to read N bytes of data starting
16 reading 4 bytes of data from address 0x10005 would be an unaligned memory
19 The above may seem a little vague, as memory access can happen in different
21 or write a number of bytes to or from memory (e.g. movb, movw, movl in x86
23 which will compile to multiple-byte memory access instructions, namely when
31 When accessing N bytes of memory, the base memory address must be evenly
38 of memory access. However, we must consider ALL supported architectures;
46 The effects of performing an unaligned memory access vary from architecture
50  - Some architectures are able to perform unaligned memory accesses
58  - Some architectures are not capable of unaligned memory access, but will
59    silently perform a different memory access to the one that was requested,
63 memory accesses to happen, your code will not work correctly on certain
72 memory addresses of certain variables, etc.
84 Let us assume that an instance of the above structure resides in memory
102 will never cause an unaligned access, because all memory addresses are evenly
108 resident memory size of structure instances. The optimal layout of the
130 the memory access in a way that does not cause unaligned access. Of course,
140 that can cause an unaligned memory access. The following function taken
160 able to access memory on arbitrary boundaries, the reference to a[0] causes
161 2 bytes (16 bits) to be read from memory starting at address addr1.
207 To avoid the unaligned memory access, you would rewrite it as follows:
218 memory and you wish to avoid unaligned access, its usage is as follows:
222 These macros work for memory accesses of any length (not just 32 bits as
224 aligned memory, using these macros to access unaligned memory can be costly in