Stas Sergeev

``` $ test/test_dos.py PPDOSGITTestCase.test_fpu_qemu_f2xm1_SIM_SIM Test PP-DOS-GIT FPU (Qemu) f2xm1 SIM_SIM ... ERROR ====================================================================== ERROR: Test PP-DOS-GIT FPU (Qemu) f2xm1 SIM_SIM ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/stas/src/dosemu2/test/fpu/qemu.py", line 42,...

Would you like to add some makefile targets, so that instead of running test_dos.py directly with broken deps, I'd run it via make, getting the deps built as needed?

There are obviously the failures in the test-case itself: ``` FAIL: f2xm1 0xb.3cae6b3899e20cep-5, expected 0x8.d1949341f4b6bafp-5 or 0x8.d1949341f4b6bbp-5, got 0x8.d1949341f4b6bb1p-5\r\n ``` Note that the last 2 digits do match: `0x8.d1949341f4b6bbp-5` matches...

Instead of the literal comparison, you just need to subtract reply from expected answer, take absolute value and make sure it doesn't exceed the threshold.

Maybe you can keep the literal comparisons for native cpu backends (like kvm) where the exact match is guaranteed by testing the physical CPU and using the physical CPU for...

Or you can try just avoid the last digit by the use of the different output formatter.

https://www.thegeekdiary.com/what-are-sparse-files-in-linux/ According to this, ls shows the full size of a sparse file. So: ``` $ mkfatimage16 -f a.img -k 10240 $ ls -l a.img -rw-rw-r-- 1 stas stas 33920...

I won't, I've got a new toy coding with ia16-gcc for 32bits. :) Eventually I'll (probably) make it public.

> I'll have a look later, unless you get to it first. Did this happen?

So -k is completely ignored w/o -p? Also I wonder who implemented -p via lseek() instead of ftruncate()...