Lines Matching refs:order
1828 >0xc byte 00 \b, DOS 3.3 sector order
1831 >0xc byte 01 \b, ProDOS sector order
1918 # that I could find. The 1 and 2 really mean "order in which you defined
1930 # row- or column-order recalculation; the A or M means automatic or manual
2433 # coding indicated by setting the high-order bit of the leftmost byte
2484 # byte order as the machine running "file" with "cpio archive", and
2485 # to indicate archives produced on machines with the opposite byte order
2506 # They were written with binary values in host byte order, and
5635 # "VAX-order" and "VAX-order2"?
5639 0 short 03401 VAX-order 68K Blit (standalone) executable
5642 0 short 03001 VAX-order 68k Blit mpx/mux executable
6287 # XXX - what byte order does the Clipper use?
6724 # This magic number is byte-order-independent.
6729 # byte-order independent, and one of which is byte-order dependent?
8250 # Hash 1.85/1.86 databases store metadata in network byte order.
8251 # Btree 1.85/1.86 databases store the metadata in host byte order.
8252 # Hash and Btree 2.X and later databases store the metadata in host byte order.
8259 >>4 belong >0 (Hash, version %d, native byte-order)
8273 >>4 belong >0 (Hash, version %d, native byte-order)
8276 >4 long >0 (Btree, version %d, native byte-order)
8283 >16 long >0 (Hash, version %d, native byte-order)
8290 >16 long >0 (Btree, version %d, native byte-order)
8297 >16 long >0 (Queue, version %d, native byte-order)
8305 >16 long >0 (Log, version %d, native byte-order)
9228 # We specify both byte orders in order to recognize byte-swapped dumps.
9458 # We have to check the byte order flag to see what byte order all the
9760 >5 byte 0 invalid byte order
9791 # XXX - needs to have the byte order specified (NS32K was little-endian,
12990 # All new-style FreeBSD magic numbers are in host byte order (i.e.,
13106 # 28: low order byte of the current PTD entry, always 0 since the
14469 # XXX - somebody should figure out whether any byte order needs to be
14480 # practice in order to avoid collisions.
14501 # The "misc" stuff needs a byte order; the archives look suspiciously
14511 0 long 01203604016 TML 0123 byte-order format
14512 0 long 01702407010 TML 1032 byte-order format
14513 0 long 01003405017 TML 2301 byte-order format
14514 0 long 01602007412 TML 3210 byte-order format
14758 # Unfortunately, HP-UX uses corehead blocks without specifying the order
14764 # The only observed order in real core files is KERNEL, EXEC, FORMAT, PROC
14765 # but we include all 6 variations of the order of the first 3, and
16716 # ulequad order: 0xGGGGGGGGRRRRRRRR, 0xAAAAAAAABBBBBBBB
17837 # "long" magic is a better practice in order to avoid collisions.
18477 # yes, this is separate from the low-order magic number bit
20136 # XXX - byte order?
20180 # The high-order word is an internal value that is implementation specific.
20181 # The low-order word is MINIDUMP_VERSION 0xA793
20211 # XXX - byte order?
22286 >>0x400A string \0\0\0\0\0\0 MSX ROM with nonstandard page order
22294 >>0x800A string \0\0\0\0\0\0 MSX ROM with nonstandard page order
22302 >0x3C008 string \0\0\0\0\0\0\0\0 MSX MegaROM with nonstandard page order
22487 # All new-style magic numbers are in network byte order.
22872 # We have to check the byte order flag to see what byte order all the
22897 >5 byte 0 invalid byte order
22910 >>18 leshort 1 AT&T WE32100 - invalid byte order,
22911 >>18 leshort 2 SPARC - invalid byte order,
22913 >>18 leshort 4 Motorola 68000 - invalid byte order,
22914 >>18 leshort 5 Motorola 88000 - invalid byte order,
22917 >>18 leshort 8 MIPS R3000_BE - invalid byte order,
22918 >>18 leshort 9 Amdahl - invalid byte order,
22920 >>18 leshort 11 RS6000 - invalid byte order,
22921 >>18 leshort 15 PA-RISC - invalid byte order,
22943 >>18 beshort 3 Intel 80386 - invalid byte order,
22946 >>18 beshort 6 Intel 80486 - invalid byte order,
22950 >>18 beshort 10 MIPS R3000_LE - invalid byte order,
23359 # XXX - byte order?
23594 >4 byte >0 (net-order %d)
24279 # XXX - byte order? Paging Hokey....
24535 # XXX - byte order?
24553 # two bytes of magic followed by "\r\n" in little endian order
25376 # XXX - byte order?
26275 # XXX - byte order?
27175 # ncurses6 (2015) uses this format, ignoring byte-order
