/external/pcre/ |
config.sub | 802 os=-coff 1004 os=-coff 1203 z8k-*-coff) 1207 z80-*-coff) 1333 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1519 os=-coff 1522 os=-coff 1525 os=-coff 1528 os=-coff [all...] |
/external/srtp/ |
config.sub | 672 os=-coff 759 os=-coff 848 os=-coff 962 os=-coff 966 os=-coff 970 os=-coff 1039 z8k-*-coff) 1163 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1332 os=-coff 1366 os=-coff [all...] |
/external/strace/ |
config.sub | 676 os=-coff 763 os=-coff 852 os=-coff 966 os=-coff 970 os=-coff 974 os=-coff 1047 z8k-*-coff) 1171 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1343 os=-coff 1377 os=-coff [all...] |
/external/tcpdump/ |
config.sub | 654 os=-coff 745 os=-coff 834 os=-coff 948 os=-coff 952 os=-coff 956 os=-coff 1025 z8k-*-coff) 1145 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1311 os=-coff 1345 os=-coff [all...] |
/external/valgrind/main/ |
config.sub | 752 os=-coff 948 os=-coff 1069 os=-coff 1073 os=-coff 1077 os=-coff 1154 z8k-*-coff) 1158 z80-*-coff) 1281 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1464 os=-coff 1501 os=-coff [all...] |
/ndk/sources/host-tools/sed-4.2.1/build-aux/ |
config.sub | 752 os=-coff 948 os=-coff 1069 os=-coff 1073 os=-coff 1077 os=-coff 1154 z8k-*-coff) 1158 z80-*-coff) 1281 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1464 os=-coff 1501 os=-coff [all...] |
/prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/share/info/ |
bfd.info | 79 Intel Oregon, for interoperability of applications on their COFF and 89 coff. 139 coff, but loses efficiency when applied to formats such as S-records and 187 Another example is COFF section names. COFF files may contain an 213 linking or copying big endian COFF to little endian COFF, or `a.out' to 263 This information would be useless to most COFF debuggers; the 268 example, COFF, IEEE, Oasys) and the type is simple enough to fit 283 byte being written to a 68k COFF file, even though 68k COFF has n [all...] |
/prebuilt/darwin-x86/toolchain/arm-linux-androideabi-4.4.x/share/info/ |
bfd.info | 79 Intel Oregon, for interoperability of applications on their COFF and 89 coff. 139 coff, but loses efficiency when applied to formats such as S-records and 187 Another example is COFF section names. COFF files may contain an 213 linking or copying big endian COFF to little endian COFF, or `a.out' to 263 This information would be useless to most COFF debuggers; the 268 example, COFF, IEEE, Oasys) and the type is simple enough to fit 283 byte being written to a 68k COFF file, even though 68k COFF has n [all...] |
/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/share/info/ |
bfd.info | 78 Intel Oregon, for interoperability of applications on their COFF and 88 coff. 138 coff, but loses efficiency when applied to formats such as S-records and 186 Another example is COFF section names. COFF files may contain an 212 linking or copying big endian COFF to little endian COFF, or `a.out' to 262 This information would be useless to most COFF debuggers; the 267 example, COFF, IEEE, Oasys) and the type is simple enough to fit 282 byte being written to a 68k COFF file, even though 68k COFF has n [all...] |
/prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/share/info/ |
bfd.info | 78 Intel Oregon, for interoperability of applications on their COFF and 88 coff. 138 coff, but loses efficiency when applied to formats such as S-records and 186 Another example is COFF section names. COFF files may contain an 212 linking or copying big endian COFF to little endian COFF, or `a.out' to 262 This information would be useless to most COFF debuggers; the 267 example, COFF, IEEE, Oasys) and the type is simple enough to fit 282 byte being written to a 68k COFF file, even though 68k COFF has n [all...] |
/external/llvm/include/llvm/MC/ |
MCWin64EH.h | 86 // This emits the unwind info sections (.pdata and .xdata in PE/COFF).
|
/external/llvm/lib/MC/ |
MCObjectWriter.cpp | 78 // On ELF and COFF A - B is absolute if A and B are in the same section.
|
/external/llvm/lib/Object/ |
Binary.cpp | 21 #include "llvm/Object/COFF.h"
|
/external/llvm/lib/Target/MBlaze/MCTargetDesc/ |
MBlazeMCTargetDesc.cpp | 89 llvm_unreachable("MBlaze does not support Windows COFF format");
|
/hardware/ti/omap3/dspbridge/inc/ |
dbdcddef.h | 56 * - DCD_REGISTER_SECTION identifies the COFF section where the UUID of
|
/hardware/ti/omap3/dspbridge/libbridge/inc/ |
dbdcddef.h | 56 * - DCD_REGISTER_SECTION identifies the COFF section where the UUID of
|
/prebuilt/darwin-x86/toolchain/arm-eabi-4.4.0/info/ |
bfd.info | 79 Intel Oregon, for interoperability of applications on their COFF and 89 coff. 139 coff, but loses efficiency when applied to formats such as S-records and 187 Another example is COFF section names. COFF files may contain an 213 linking or copying big endian COFF to little endian COFF, or `a.out' to 263 This information would be useless to most COFF debuggers; the 268 example, COFF, IEEE, Oasys) and the type is simple enough to fit 283 byte being written to a 68k COFF file, even though 68k COFF has n [all...] |
/prebuilt/darwin-x86/toolchain/arm-eabi-4.4.3/info/ |
bfd.info | 79 Intel Oregon, for interoperability of applications on their COFF and 89 coff. 139 coff, but loses efficiency when applied to formats such as S-records and 187 Another example is COFF section names. COFF files may contain an 213 linking or copying big endian COFF to little endian COFF, or `a.out' to 263 This information would be useless to most COFF debuggers; the 268 example, COFF, IEEE, Oasys) and the type is simple enough to fit 283 byte being written to a 68k COFF file, even though 68k COFF has n [all...] |
/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/info/ |
bfd.info | 78 Intel Oregon, for interoperability of applications on their COFF and 88 coff. 138 coff, but loses efficiency when applied to formats such as S-records and 186 Another example is COFF section names. COFF files may contain an 212 linking or copying big endian COFF to little endian COFF, or `a.out' to 262 This information would be useless to most COFF debuggers; the 267 example, COFF, IEEE, Oasys) and the type is simple enough to fit 282 byte being written to a 68k COFF file, even though 68k COFF has n [all...] |
/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/info/ |
bfd.info | 78 Intel Oregon, for interoperability of applications on their COFF and 88 coff. 138 coff, but loses efficiency when applied to formats such as S-records and 186 Another example is COFF section names. COFF files may contain an 212 linking or copying big endian COFF to little endian COFF, or `a.out' to 262 This information would be useless to most COFF debuggers; the 267 example, COFF, IEEE, Oasys) and the type is simple enough to fit 282 byte being written to a 68k COFF file, even though 68k COFF has n [all...] |
/external/bison/build-aux/ |
config.sub | 689 os=-coff 864 os=-coff 978 os=-coff 982 os=-coff 986 os=-coff 1059 z8k-*-coff) 1180 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1353 os=-coff 1387 os=-coff 1480 os=-coff [all...] |
/external/chromium/sdch/open-vcdiff/ |
config.sub | 705 os=-coff 893 os=-coff 1014 os=-coff 1018 os=-coff 1022 os=-coff 1095 z8k-*-coff) 1217 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1397 os=-coff 1434 os=-coff 1527 os=-coff [all...] |
/external/chromium/third_party/libevent/ |
config.sub | 725 os=-coff 921 os=-coff 1042 os=-coff 1046 os=-coff 1050 os=-coff 1127 z8k-*-coff) 1249 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1429 os=-coff 1466 os=-coff 1559 os=-coff [all...] |
/external/dropbear/ |
config.sub | 701 os=-coff 889 os=-coff 1010 os=-coff 1014 os=-coff 1018 os=-coff 1091 z8k-*-coff) 1213 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1393 os=-coff 1430 os=-coff 1523 os=-coff [all...] |
/external/expat/conftools/ |
config.sub | 701 os=-coff 889 os=-coff 1007 os=-coff 1011 os=-coff 1015 os=-coff 1088 z8k-*-coff) 1210 | -ptx* | -coff* | -ecoff* | -winnt* | -domain* | -vsta* \ 1390 os=-coff 1424 os=-coff 1517 os=-coff [all...] |