Author Topic: jWasm for DOS version 2.13 for testing  (Read 2178 times)

Gunther

  • Member
  • *****
  • Posts: 3515
  • Forgive your enemies, but never forget their names
jWasm for DOS version 2.13 for testing
« on: July 24, 2015, 01:39:21 AM »
I've successful compiled jWasm for DOS, version 2.13. It supports now AVX and AVX2 - thank you, Habran for the excellent work.

JWASM.EXE runs in DOS 32bit protected-mode. It requires a 80386 cpu and needs a MS-DOS v5 compatible DOS to run. Long filenames (LFN) are supported. It won't run on 64-bit Windows.

I've tested the EXE under plain DOS and under virtual machines (VMWare and VirtualBox). The EXE is compiled with gcc for DOS, version 4.7.3.

Habran is currently working on a major update, which supports AVX512 etc. He'll need a bit time for that. My contribution was very small. I did only help a bit by the compilation. I'll try next to compile the BSD and Linux version. Probably I can provide a bit Web space for downloading the binaries and sources, but that will take a little while.

Some test reports for version 2.13 would be fine. Have fun.

Gunther
Get your facts first, and then you can distort them.

FORTRANS

  • Member
  • ****
  • Posts: 944
Re: jWasm for DOS version 2.13 for testing
« Reply #1 on: July 29, 2015, 06:10:48 AM »
Hi,

   Tested trivially, and it seems to work.  Is there something you
are looking for?

Regards,

Steve N.

Gunther

  • Member
  • *****
  • Posts: 3515
  • Forgive your enemies, but never forget their names
Re: jWasm for DOS version 2.13 for testing
« Reply #2 on: July 29, 2015, 10:15:36 PM »
Steve,

thank you for testing. Habran included the new AVX and AVX2 instructions into that version. By the way, I've forwarded a PM to you.

Gunther
Get your facts first, and then you can distort them.

nidud

  • Member
  • *****
  • Posts: 1370
    • https://github.com/nidud/asmc
Re: jWasm for DOS version 2.13 for testing
« Reply #3 on: August 01, 2015, 06:54:16 AM »
Hi Gunther,

I tested using the regress test for ASMC.EXE based on output from JWASM version 2.12pre.

Running the test with 2.12pre I get this output (one existing bug):
Code: [Select]
..\asm\HLL3.ASM(11) : Error A2102: Symbol not defined : @C0002
HLL3.BIN: No such file or directory

Running the test with your version I get this output:
Code: [Select]
00000441: F1 F9
00000443: F8 F9
00000446: F1 F9
00000448: D8 D9
0000044B: F1 F9
0000044D: D0 D1
00000450: F1 F9
00000452: D0 D1
00000455: F1 F9
00000457: D0 D1
10 unequal bytes found cmp(AVX1.BIN, ..\exp\AVX1.EXP)
0000000A: 85 23
1 unequal bytes found cmp(EXPANS37.BIN, ..\exp\EXPANS37.EXP)
00000000: 85 23
00000006: 85 23
2 unequal bytes found cmp(EXPANS40.BIN, ..\exp\EXPANS40.EXP)
..\asm\HLL3.ASM(11) : Error A2102: Symbol not defined : @C0002
HLL3.BIN: No such file or directory
INVOK644.BIN, ..\exp\INVOK644.EXP: file sizes differ
00000000: 33 B9
00000001: C9 00
00000002: E8 00
00000003: F9 00
00000004: FF 00
00000005: FF E8
00000006: FF F6
00000007: 41 FF
00000008: B9 FF
00000009: 04 FF
10 unequal bytes found cmp(INVOK646.BIN, ..\exp\INVOK646.EXP)
INVOK649.BIN, ..\exp\INVOK649.EXP: file sizes differ
INVOK64A.BIN, ..\exp\INVOK64A.EXP: file sizes differ
00000048: 85 23
00000051: 85 23
2 unequal bytes found cmp(RTCOND3.BIN, ..\exp\RTCOND3.EX
VARAR642.BIN, ..\exp\VARAR642.EXP: file sizes differ
VARARG64.BIN, ..\exp\VARARG64.EXP: file sizes differ
EXPR5.ERR, ..\exp\EXPR5.EXP: file sizes differ
FLOAT8.ERR, ..\exp\FLOAT8.EXP: file sizes differ
MACRO27.ERR, ..\exp\MACRO27.EXP: file sizes differ
PROC643.OBJ, ..\exp\PROC643.EXP: file sizes differ
00000170: 33 32
1 unequal bytes found cmp(DBGCV.OBJ, ..\exp\DBGCV.EXP)
0000001B: 00 78
0000001C: 00 BF
0000001D: 21 43
0000001E: EC 43
00000031: B5 05
5 unequal bytes found cmp(LINNUM.OBJ, ..\exp\LINNUM.EXP)

These errors may be related to changes done by habran, so new EXP files should be made from a bug-free version to verify these results.

I attached the test bed used so new expected output to the EXP directory could be build. This is done by copy JWASM to the TMP directory and then run BUILDEXP.CMD. After this is done just copy the JWASM version you want to test into the TMP directory and run RUNTEST.CMD.

The environment for the test is controlled by the Commander so additional tools should be copied to the PATH directory to avoid conflict during the test. You may aslo use Shift-F6 to edit the environment directly or use the INI file to set PATH.

You need JWLINK and optionally a newer version of LINK for the SAFESEH test.

Gunther

  • Member
  • *****
  • Posts: 3515
  • Forgive your enemies, but never forget their names
Re: jWasm for DOS version 2.13 for testing
« Reply #4 on: August 01, 2015, 07:27:30 AM »
Hi nidud,

These errors may be related to changes done by habran, so new EXP files should be made from a bug-free version to verify these results.

thank you for doing the regression test.  :t Good job. I hope that Habran will read your post, because I've onle made the compilation. I'll forward a PM to him for sure.

Gunther
Get your facts first, and then you can distort them.

Gunther

  • Member
  • *****
  • Posts: 3515
  • Forgive your enemies, but never forget their names
Re: jWasm for DOS version 2.13 for testing
« Reply #5 on: August 02, 2015, 02:25:35 AM »
Hi nidud,

I've done some communication with Habran via PM. He's very occupied with finishing the AVX512 material. That's not so easy (all the new registers and instructions). After that he'll fine tuning the entire assembler.

Gunther
Get your facts first, and then you can distort them.