News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests

Main Menu

where is .data? segment?

Started by markallyn, November 07, 2017, 04:14:08 AM

Previous topic - Next topic

hutch--

Mark,

You may share my humour here in that ML64 is to put it kindly, rather rudimentary as well as badly documented and grossly intolerant to minor variations in notation. Where 32 bit ML had all sorts of redundancies to make it (ab)user friendly, ML64 has not and this is primarily because it is an industrial software tool rather than consumer software. You either use it the right way or it explodes in your face.

Under the old notation you would use something like ".MODEL FLAT, FASTCALL" but as there is no other option in Win64, that notation is redundant and it is not supported. As far as directives like PUBLIC, always put directives OUTSIDE of other sections as the parsing code in ML64 does nothing more than what it has to when you build an object module.

The setting that IS important is in the linker settings, if you specify /LARGEADDRESSAWARE and do not use some of the older 32 bit style constructions that tell you to turn it off, you get the 64 bit address range rather than a badly warmed over 32 bit address range and this is important.

aw27

Quote from: qWord on November 09, 2017, 07:42:21 AM
what I'm missing?
You are not missing anything, it is Microsoft that is losing parts and pieces like an old jalopy  :lol: without anyone inside the organization noticing.
What I posted builds perfectly with JWASM and UASM.
jwasm -c -Zp8 -win64 foo.asm