Page 1 of 1

NASM 2.00 is Here!!!

Posted: Wed Nov 28, 2007 9:09 pm
by SpooK
After 7 months of intense development, the NASM team brings you NASM 2.0!!!

This version of NASM supercedes version 0.98.39 (and Apple's 0.98.40) and introduces full 64-bit (x86-64/x64/AMD64/Intel 64) architecture and object file support.

We have also addressed quite a few bugs and feature requests along the way.

We hope you sincerely enjoy the latest version of NASM and what it has to offer :)

LINK: http://nasm.sourceforge.net/

Posted: Thu Nov 29, 2007 2:48 am
by AJ
I'll switch to it right away from 0.98.x. Thanks for the notification.

Adam

Posted: Thu Nov 29, 2007 2:50 am
by JamesM
Me too. Cheers Spook. Which bits did you work on btw?

Posted: Thu Nov 29, 2007 4:00 am
by AndrewAPrice
What ever happened to NASM 1.x?

Posted: Thu Nov 29, 2007 3:23 pm
by SpooK
JamesM wrote:Me too. Cheers Spook. Which bits did you work on btw?
I added most x86-64 support as close to AMD64 specifications as possible. This included familiarizing myself with NASM source code, adding the new instructions and registers to the "database" by hand, finding the most efficient way to integrate the 64-bit specifications, reworking how effective addresses were generated, adding general 64-bit object file generation support, adding the Win64 object format, and a few code cleanups and bug fixes.

Charles Crayne implemented ELF64 support, some important fixes, changes to the documentation, and some other general modifications.

Frank Kotler helped keep DOS users in the loop, kept SourceForge updated, and did some bug finding/fixing.

H. Peter Anvin did most of the overall work, the bug fixes, huge code optimization, got NDISASM synced with NASM, and setup the neat nightly snapshot system that generates binaries for the most popular/common operating systems.

As a team, we helped reveal some bugs/flaws in YASM and diStorm64 as a result of our work. I think all of them have been fixed by now. Just an extremely productive 7 months, overall.
MessiahAndrw wrote:What ever happened to NASM 1.x?
It was commonly agreed that NASM was left pre 1.0 way too long.

0.98.* should have actually been 1.*, so we decided to just move to 2.0 :)