Quick way to Update to Masm(ml.exe) 9

[drizz]

MSLink : use /MERGE:.data=.rdata command
MSLink : use /FILEALIGN:512 command

I can't get those to work. They get (silently) ignored ? Using MS linker  9.00.21022.08 , will try others, too.

I compare the resulting executables and the only difference is the timestamp  :eek

I only meant /MERGE as an example, i wrote the commands by heart, should be
>/MERGE:.rdata=.data< or better >/MERGE:.rdata=.text<
and for the size squeezers:
/FILEALIGN:512 /MERGE:.rdata=.text /MERGE:.rsrc=.text  /MERGE:.data=.text /MERGE:.bss=.text /SECTION:.text,RWE

oh btw FILEALIGN is an undocumented switch but should works with all link versions. Check the resulting PE with LordPE.

[BlackVortex]

Just tested (properly this time) and drizz is correct as always.

Also, more on-topic, can someone please upload somewhere latest MS link.exe and link.exe.config ? I have Visual Studio 9.0 but my version is earlier, it reports 9.00.21022.08.

(or PM)

[jj2007]

oh btw FILEALIGN is an undocumented switch but should works with all link versions. Check the resulting PE with LordPE.

The switch works but does not produce smaller executables because its default is already 512 bytes. Try putting /FILEALIGN:1024...
The other switches work partially but do not seem to be able to produce the same size as polink with default switches.
Testbed attached.
And, no, I don't want to start a link vs polink debate, but I am curious to know what is fact and what is fiction.

[attachment deleted by admin]

[BlackVortex]

I confirm jj's findings. Polink is more efficient. I just wish the windows loader would accept a file alignment of 256, or a switch to omit the DOS header and stub.  Just for kicks    :green2

[drizz]

I forgot something :) I have my link patched not to produce "Rich Signature"
I can also run latest ml without manifests and winsxs dependency but those are topics for some other forum :)