Lines Matching +full:4 +full:- +full:way

24 For example, reading 4 bytes of data from address 0x10004 is fine, but
25 reading 4 bytes of data from address 0x10005 would be an unaligned memory
32 which will compile to multiple-byte memory access instructions, namely when
48 writing code that satisfies natural alignment requirements is the easiest way
59  - Some architectures are able to perform unaligned memory accesses
61  - Some architectures raise processor exceptions when unaligned accesses
64  - Some architectures raise processor exceptions when unaligned accesses
67  - Some architectures are not capable of unaligned memory access, but will
98 by 4 (remember, we're reading a 4 byte value here).
131 structure type. This GCC-specific attribute tells the compiler never to
139 the memory access in a way that does not cause unaligned access. Of course,
141 non-packed case, so the packed attribute should only be used when avoiding
157 		   ((*(const u16 *)(addr1 + 4)) ^ (*(const u16 *)(addr2 + 4)));
177 16-bit-aligned addresses. It is up to the caller to ensure this alignment or
178 not use this function at all. This alignment-unsafe function is still useful
193 to an address that is not evenly divisible by 4.
205 The easiest way to avoid unaligned access is to use the get_unaligned() and
240 Due to the byte-wise nature of this operation, unaligned accesses are avoided.
247 header is aligned on a four-byte boundary to optimise the IP stack. For
251 DMA to an address which can be expressed as 4*n + 2. One notable exception
256 4*n+2 or non-ethernet hardware, this can be a problem, and it is then