Author Topic: NASM 2.00rc1  (Read 1089 times)

0 Members and 1 Guest are viewing this topic.

Offline SpooK

  • Community Staff
  • ASM Fanatic
  • *****
  • Posts: 2297
  • Country: us
    • Personal Homepage
NASM 2.00rc1
« on: 2007-11-17 06:40:23 »
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 :)

Offline Dite

  • Code Warrior
  • **
  • Posts: 115
    • BLog
Re: NASM 2.00rc1
« Reply #1 on: 2007-11-17 12:33:08 »
It's ok, but It would be better if you had fixed those annoying warning messages. Probably they aren't improtant

Quote
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
PhiOS
"Some people have got a mental horizon of radius zero and call it their point of view." --D.Hilbert

Offline SpooK

  • Community Staff
  • ASM Fanatic
  • *****
  • Posts: 2297
  • Country: us
    • Personal Homepage
Re: NASM 2.00rc1
« Reply #2 on: 2007-11-17 17:32:14 »
You've should have seen the number of warnings when I first touched it :shock: