..
1shl0.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
1shl0.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
absloop-err.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
absloop-err.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
bitvect_test.c
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
charconst64.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
charconst64.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
combpath_test.c
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
data-rawvalue.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
data-rawvalue.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
duplabel-err.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
duplabel-err.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
emptydata.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
emptydata.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
equ-expand.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
equ-expand.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
expr-wide-ident.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
expr-wide-ident.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
externdef.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
externdef.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
externdef.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
floatnum_test.c
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
incbin.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
incbin.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
jmpsize1-err.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
jmpsize1-err.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
jmpsize1.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
jmpsize1.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
leb128_test.c
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
libyasm_test.sh
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
Makefile.inc
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-align1.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-align1.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-align2.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-align2.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-align3.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-align3.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-circular1-err.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-circular1-err.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-circular2-err.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-circular2-err.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-circular3-err.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-circular3-err.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-gvmat64.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-gvmat64.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-immexpand.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-immexpand.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-immnoexpand.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-immnoexpand.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-oldalign.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-oldalign.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-struc.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
opt-struc.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
reserve-err1.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
reserve-err1.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
reserve-err2.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
reserve-err2.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
splitpath_test.c
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
strucsize.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
strucsize.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
times0.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
times0.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
times-res.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
times-res.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
times-res.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
timesover-err.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
timesover-err.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
timesunder.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
timesunder.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
unary.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
unary.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
uncstring_test.c
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
value-err.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
value-err.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
value-mask.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
value-mask.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
value-mask.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
value-samesym.asm
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
value-samesym.errwarn
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
value-samesym.hex
Roughly speaking mpir should now build on an AMD64. At the present moment the config.guess doesn't distinguish a Core 2 from an AMD64 and so the same code is probably built on both.
2008-05-26 22:11:40 +00:00
c0e157e3b2