DOS ain't dead - NASM 2.10 - revised preprocessor

NASM 2.10 - revised preprocessor (Announce)

posted by RayeR , CZ, 02.05.2012, 22:43

> Have you tested that anything is actually messed up, ie that it doesn't
> work? Newer NASMs optimise better, for example, unconditional jumps are
> shortened even without explicit "short" keyword, and fitting values will
> select sign-extending instructions even without explicit "byte" keyword. (I
> think the latter is new even if you previously already specified -Ox on the
> command line, which is the default now!) For these reasons,
> byte-incompatible output might still be correct.

Yes you got it. All the differences of binary made by 2.10 seems to be jmp -> jmps that saved some bytes and shifted the entire code. I chcecked the binary in BOSH and it WORKS. I wrote in a mistake the version that chinese guy used - 2.09.07 compiled on Mar 14 2011. I suggested him to upgrade on 2.10. Hope it will solve the problem.

---
DOS gives me freedom to unlimited HW access.

Post reply

Complete thread:

NASM 2.10 - Rugxulo, 27.03.2012, 00:39 (Announce)
- NASM 2.10 - Rugxulo, 27.03.2012, 00:42
  - NASM 2.10 - marcov, 27.03.2012, 13:07
  - NASM 2.10 - revised preprocessor - ecm, 20.04.2012, 04:26
    - NASM 2.10 - revised preprocessor - RayeR, 02.05.2012, 22:06
      - NASM 2.10 - revised preprocessor - ecm, 02.05.2012, 22:16
        NASM 2.10 - revised preprocessor - RayeR, 02.05.2012, 22:43
        NASM 2.10 - revised preprocessor - ecm, 02.05.2012, 22:48
        NASM 2.10 - revised preprocessor - RayeR, 03.05.2012, 00:04
        NASM 2.10 uses "- Ox" by default - Rugxulo, 03.05.2012, 02:25
        NASM 2.10 uses "-Ox" by default - ecm, 03.05.2012, 02:37
        NASM 2.10 uses "-Ox" by default - Rugxulo, 03.05.2012, 08:18
        NASM 2.10 uses "-Ox" by default - ecm, 03.05.2012, 23:00
        NASM 2.10.01 - Rugxulo, 16.06.2012, 00:24
        NASM 2.10 - revised preprocessor - ecm, 03.05.2012, 02:26