Home
last modified time | relevance | path

Searched refs:significant (Results 1 – 25 of 50) sorted by relevance

12

/toolchain/binutils/binutils-2.25/gas/
Dflonum-mult.c85 long significant; /* TRUE when we emit a non-0 littlenum */ in flonum_multip() local
116 significant = 0; in flonum_multip()
142 significant |= work; in flonum_multip()
143 if (significant || P < 0) in flonum_multip()
Dconfigure.com178 /* Define to 1 if your processor stores words with the most significant byte
DCONTRIBUTORS108 you've contributed significant work and are not mentioned on this list, and
Dconfig.in348 significant byte first (like Motorola and SPARC, unlike Intel). */
/toolchain/binutils/binutils-2.25/include/aout/
Dstab.def30 /* Global variable. Only the name is significant.
34 /* Function name for BSD Fortran. Only the name is significant.
50 /* Name of main routine. Only the name is significant. */
158 In an object file, only the name is significant.
172 In an object file, there is no significant data in this entry.
203 /* Begin named common block. Only the name is significant. */
206 /* End named common block. Only the name is significant
/toolchain/binutils/binutils-2.25/gas/doc/
Dc-sh64.texi149 will always have the least significant bit set (i.e. they will be odd),
150 which SHcompact labels will have the least significant bit reset
161 significant bit set depending on whether the label is an SHmedia label
181 significant bit of the label's address), so such mode/isa changes should
Dc-rl78.texi59 selects the 16 least significant bits.
68 selects the 16 most significant bits.
Dc-bfin.texi151 denotes the most significant ("High") portion. ".L" denotes the
152 least-significant portion. The subdivisions of the 40-bit registers
175 or as two independent 16-bit registers. The least significant 16 bits
177 following the register name. The most significant 16 bits are called
Dc-z80.texi129 @samp{ixh} as the least and most significant octet in @samp{ix}, and
141 The case of letters is significant in labels and symbol names. The case
Dc-msp430.texi105 Extracts least significant word from 32-bit expression 'exp'.
108 Extracts most significant word from 32-bit expression 'exp'.
Dc-tic54x.texi407 stored most-significant word first.
440 pack starting at the current word, filling the most significant bits
502 section. The most significant word is stored first. @code{.long} and
595 most-significant bits first. Unused space is zero-filled. If a label
Dc-hppa.texi50 uses the @code{spop} instructions, or code which makes significant
Dc-vax.texi141 towards zero if the remainder is exactly half the least significant bit.
Dc-v850.texi366 value of the most significant bit of the lower 16 bits of the expression
/toolchain/binutils/binutils-2.25/ld/testsuite/ld-mips-elf/
Djaloverflow.d11 # most significant four bits.
/toolchain/binutils/binutils-2.25/ld/emultempl/
Dcr16elf.em70 a significant amount of time and memory. */
Dm68kelf.em98 a significant amount of time and memory. */
Dm68kcoff.em87 a significant amount of time and memory. */
/toolchain/binutils/binutils-2.25/gold/
Dconfig.in264 significant byte first (like Motorola and SPARC, unlike Intel). */
/toolchain/binutils/binutils-2.25/libiberty/
Dconfig.in489 significant byte first (like Motorola and SPARC, unlike Intel). */
/toolchain/binutils/binutils-2.25/opcodes/po/
Dpt_BR.po321 msgid "ignoring least significant bits in branch offset"
Dzh_CN.po650 msgid "ignoring least significant bits in branch offset"
Did.po1258 #~ msgid "ignoring least significant bits in branch offset"
1259 #~ msgstr "mengabaikan least significant bit dalam offset cabang"
Dtr.po640 msgid "ignoring least significant bits in branch offset"
Dsv.po670 msgid "ignoring least significant bits in branch offset"

12