| /external/chromium_org/third_party/yasm/source/patched-yasm/modules/arch/x86/tests/ |
| genopcode.asm | 119 fbld [100] label
120 fbld tword [10] label
|
| /external/valgrind/main/memcheck/tests/x86/ |
| more_x86_fp.c | 142 asm("fbld %1" : "=t" (b) : "m" (bcd[0]));
|
| /external/libvpx/libvpx/examples/includes/geshi/geshi/ |
| asm.php | 81 'f2xm1','fabs','fadd','faddp','fbld','fbstp','fchs','fclex','fcom','fcomp','fcompp','fdecstp',
|
| /external/valgrind/main/memcheck/tests/amd64/ |
| more_x87_fp.c | 152 asm("fbld %1" : "=t" (b) : "m" (bcd[0]));
|
| /prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6/share/man/man1/ |
| arm-eabi-ld.1 | 139 \&\fBld\fR combines a number of object and archive files, relocates
141 compiling a program is to run \fBld\fR.
143 \&\fBld\fR accepts Linker Command Language files written in
148 \&\fBld\fR entry in \f(CW\*(C`info\*(C'\fR for full details on the command
151 This version of \fBld\fR uses the general purpose \s-1BFD\s0 libraries
152 to operate on object files. This allows \fBld\fR to read, combine, and
160 \&\fBld\fR continues executing, allowing you to identify other errors
163 The \s-1GNU\s0 linker \fBld\fR is meant to cover a broad range of situations,
170 For instance, a frequent use of \fBld\fR is to link standard Unix
178 This tells \fBld\fR to produce a file called \fIoutput\fR as th
[all...] |
| arm-eabi-objdump.1 | 335 \&\fBld\fR. However, some object file formats, such as a.out, do not
337 although \fBld\fR relocates the sections correctly, using \fBobjdump
|
| /prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.6/share/man/man1/ |
| arm-linux-androideabi-ld.1 | 139 \&\fBld\fR combines a number of object and archive files, relocates
141 compiling a program is to run \fBld\fR.
143 \&\fBld\fR accepts Linker Command Language files written in
148 \&\fBld\fR entry in \f(CW\*(C`info\*(C'\fR for full details on the command
151 This version of \fBld\fR uses the general purpose \s-1BFD\s0 libraries
152 to operate on object files. This allows \fBld\fR to read, combine, and
160 \&\fBld\fR continues executing, allowing you to identify other errors
163 The \s-1GNU\s0 linker \fBld\fR is meant to cover a broad range of situations,
170 For instance, a frequent use of \fBld\fR is to link standard Unix
178 This tells \fBld\fR to produce a file called \fIoutput\fR as th
[all...] |
| arm-linux-androideabi-objdump.1 | 335 \&\fBld\fR. However, some object file formats, such as a.out, do not
337 although \fBld\fR relocates the sections correctly, using \fBobjdump
|
| /prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/share/man/man1/ |
| arm-eabi-ld.1 | 139 \&\fBld\fR combines a number of object and archive files, relocates
141 compiling a program is to run \fBld\fR.
143 \&\fBld\fR accepts Linker Command Language files written in
148 \&\fBld\fR entry in \f(CW\*(C`info\*(C'\fR for full details on the command
151 This version of \fBld\fR uses the general purpose \s-1BFD\s0 libraries
152 to operate on object files. This allows \fBld\fR to read, combine, and
160 \&\fBld\fR continues executing, allowing you to identify other errors
163 The \s-1GNU\s0 linker \fBld\fR is meant to cover a broad range of situations,
170 For instance, a frequent use of \fBld\fR is to link standard Unix
178 This tells \fBld\fR to produce a file called \fIoutput\fR as th
[all...] |
| arm-eabi-objdump.1 | 335 \&\fBld\fR. However, some object file formats, such as a.out, do not
337 although \fBld\fR relocates the sections correctly, using \fBobjdump
|
| /prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/share/man/man1/ |
| arm-linux-androideabi-ld.1 | 139 \&\fBld\fR combines a number of object and archive files, relocates
141 compiling a program is to run \fBld\fR.
143 \&\fBld\fR accepts Linker Command Language files written in
148 \&\fBld\fR entry in \f(CW\*(C`info\*(C'\fR for full details on the command
151 This version of \fBld\fR uses the general purpose \s-1BFD\s0 libraries
152 to operate on object files. This allows \fBld\fR to read, combine, and
160 \&\fBld\fR continues executing, allowing you to identify other errors
163 The \s-1GNU\s0 linker \fBld\fR is meant to cover a broad range of situations,
170 For instance, a frequent use of \fBld\fR is to link standard Unix
178 This tells \fBld\fR to produce a file called \fIoutput\fR as th
[all...] |
| arm-linux-androideabi-objdump.1 | 335 \&\fBld\fR. However, some object file formats, such as a.out, do not
337 although \fBld\fR relocates the sections correctly, using \fBobjdump
|
| /external/chromium_org/third_party/mesa/src/src/mesa/x86/ |
| assyntax.h | 695 #define FBLD(a) CHOICE(fbld a, fbld a, fbld a)
[all...] |
| /external/mesa3d/src/mesa/x86/ |
| assyntax.h | 695 #define FBLD(a) CHOICE(fbld a, fbld a, fbld a)
[all...] |
| /external/llvm/test/MC/X86/ |
| x86-32-coverage.s | 395 // CHECK: fbld 3735928559(%ebx,%ecx,8)
396 fbld 0xdeadbeef(%ebx,%ecx,8)
[all...] |
| /external/llvm/lib/Target/X86/ |
| X86InstrFPStack.td | 300 def FBLDm : FPI<0xDF, MRM4m, (outs), (ins f32mem:$src), "fbld\t$src">;
[all...] |
| /external/elfutils/libcpu/defs/ |
| i386 | 255 11011111,{mod}100{r_m}:fbld {mod}{r_m}
[all...] |
| /external/valgrind/main/VEX/test/ |
| test-amd64.c | 672 asm("fbld %1" : "=t" (b) : "m" (bcd[0]));
[all...] |
| test-i386.c | 634 asm("fbld %1" : "=t" (b) : "m" (bcd[0]));
[all...] |
| /external/valgrind/main/perf/ |
| tinycc.c | [all...] |
| /external/chromium_org/third_party/yasm/source/patched-yasm/ |
| x86insn_nasm.gperf | 189 fbld, fbldstp_insn, 1, SUF_Z, 0x04, 0, 0, 0, CPU_FPU, 0, 0
[all...] |
| /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/bin/ |
| i686-linux-objdump | |
| /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/i686-linux/bin/ |
| objdump | |
| /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/bin/ |
| i686-linux-objdump | |
| /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/i686-linux/bin/ |
| objdump | |
