Searched refs:boundary (Results 1 – 25 of 138) sorted by relevance
123456
65 # double word access that crosses a 64 bit boundary69 # word access that crosses a 64 boundary76 # double word access that crosses a 128 boundary80 # word access that crosses a 128 bit boundary
6 # align section end to 16-byte boundary for easier testing on multiple targets13 # align section end to 16-byte boundary for easier testing on multiple targets
6 # align section end to 16-byte boundary for easier testing on multiple targets12 # align section end to 16-byte boundary for easier testing on multiple targets
8 # align section end to 16-byte boundary for easier testing on multiple targets19 # align section end to 16-byte boundary for easier testing on multiple targets
4 # align section end to 16-byte boundary for easier testing on multiple targets
5 # align section end to 16-byte boundary for easier testing on multiple targets
9 # align section end to 16-byte boundary for easier testing on multiple targets
10 # Round to a 16 byte boundary, for ease in testing multiple targets.
19 # align section end to 16-byte boundary for easier testing on multiple targets
4 # Align this to 256-byte boundary for easier address matching.17 # Align this to 256-byte boundary for easier address matching.
2 # The FILL-SLOT attribute ensures the next insn begins on a 32 byte boundary.4 # to a 32 bit boundary.
64 boundary (usually a page, or 128 words) if it is smaller than the65 blocking size, or to start on a page boundary if it is larger than the330 Align the section program counter on the next boundary, based on335 Align SPC to word boundary337 Align SPC to longword boundary (same as .even)339 Align SPC to page boundary357 should be aligned on a page boundary if it would otherwise cross a page358 boundary. If present, @var{alignment_flag} causes the assembler to359 allocate @var{size} on a long word boundary.406 @code{.xfloat} align the result on a longword boundary. Values are[all …]
5 # Test 10 bit pc rel reloc bad boundary.
5 # Test 10 bit pc rel reloc negative bad boundary.
5 # Test 10 bit pc rel reloc good boundary.
5 # Test 18 bit pc rel reloc negative good boundary case
5 # Test 18 bit pc rel reloc good boundary
5 # Test 10 bit pc rel reloc negative good boundary case
9 # arm-aout wants the segment padded to an 16-byte boundary;
11 @ the .text section to a 16 byte boundary.
35 #define BFD_ALIGN(this, boundary) \ argument36 ((((bfd_vma) (this) + (boundary) - 1) >= (bfd_vma) (this)) \37 ? (((bfd_vma) (this) + ((boundary) - 1)) & ~ (bfd_vma) ((boundary)-1)) \
1 # Dual-mode pairs must be aligned on an 8-byte boundary. This tests
4 # a 256MB memory segment boundary with calls to the same function on either
2 * .even == .align 1, .even 2 == longword boundary