Searched refs:constant (Results 1 – 22 of 22) sorted by relevance
52 -generate 0xe6300400 0xe6300404 -l-e-constant 0x0 4 \53 -generate 0xe630048c 0xe6300490 -l-e-constant 0x0 4 \54 -generate 0xe63005d4 0xe63005d8 -l-e-constant 0xe6304000 4 \55 -generate 0xe63006e4 0xe63006e8 -l-e-constant $2 4 \56 -generate 0xe6301154 0xe6301158 -l-e-constant 0xe6304000 4 \57 -generate 0xe6301264 0xe6301268 -l-e-constant $2 4 \69 -generate 0xe630402c 0xe6304030 -l-e-constant 0xd61f0000 474 -generate 0xe6300400 0xe6300404 -l-e-constant 0x0 4 \75 -generate 0xe630048c 0xe6300490 -l-e-constant 0x0 4 \77 -generate 0xe63006e4 0xe63006e8 -l-e-constant $2 4 \[all …]
1 # Put structs here that should be constant
6 bug in some versions of GCC. As the output size is a constant, the size
52 constant c;
21 constant or runtime detection. Used for sizing the scan data26 constant or runtime detection. Used for sizing the scan data
24 in other places easier (to avoid constant env lookup/parsing)
229 nm - memory modify (constant address)
23 Example with constant 'Vdd' value:
104 unsigned long constant; member
8 contains a constant initialized variable which holds the entry's41 Note the two '_2_' constant components in the names: their presence
72 * set ACPI constant Ones for elements
77 in nearly constant time. Instead of scanning the whole MTD device it
217 nm - memory modify (constant address)
249 nm - memory modify (constant address)
232 nm - memory modify (constant address)
320 nm - memory modify (constant address)
59 Finally, software patents pose a constant threat to the existence of
665 be used. It can be a constant or a function to get clock, eg,
799 This is useful when the text is constant.
636 nm - memory modify (constant address)
2082 in nearly constant time. Instead of scanning the whole MTD device it3138 nm - memory modify (constant address)
174 Either a constant or routine call returning the system page size.
Completed in 47 milliseconds