NASM has now approached release candidate status. All major bugs on the path to adding x64 support have been squashed.

For those who use NASM, we would appreciate testing the Latest Build in your programming environment/setup so we can attend to any more potential bugs and finally push out an official 2.0 release.

Thanks for your attention and support :)
Posted on 2007-11-17 01:40:23 by SpooK
It's ok, but It would be better if you had fixed those annoying warning messages. Probably they aren't improtant


parser.c: In function ‘parse_line’:
parser.c:837: warning: comparison between signed and unsigned
output/outobj.c: In function ‘obj_write_file’:
output/outobj.c:1998: warning: comparison between signed and unsigned
rdoff.c: In function ‘membufwrite’:
rdoff.c:101: warning: dereferencing type-punned pointer will break strict-aliasing rules
rdoff.c:103: warning: dereferencing type-punned pointer will break strict-aliasing rules
rdoff.c: In function ‘rdfloadseg’:
rdoff.c:375: warning: comparison between signed and unsigned
ldrdf.c: In function ‘write_output’:
ldrdf.c:723: warning: comparison between signed and unsigned
ldrdf.c: In function ‘processmodule’:
ldrdf.c:214: warning: ‘sconf.mergetype’ may be used uninitialized in this function
ldrdf.c:214: warning: ‘sconf.typedesc’ may be used uninitialized in this function
ldrdf.c:214: warning: ‘sconf.dowhat’ may be used uninitialized in this function
Posted on 2007-11-17 07:33:08 by Dite
You've should have seen the number of warnings when I first touched it :shock:
Posted on 2007-11-17 12:32:14 by SpooK