Compiler dead space is it all the same ?

[doppler]

Well the last couple of messages kinda proves my point.  But not exactly as I expected.  The original EXE file format was a unlinked com file expanded.  Inside the exe is a link table that describes all the absolute calls and jumps.  So a program that did a call X or jmp X would have a table entry X listing all references to X's  locations.  At load time the location of X becomes known and references are back filled.  Since windows is 95% intel architecture.  64K code segments are the norm.  Any even memory address could be the CS register location.  Never use odd address start 16/32/64 bit processors take a very bad cycles hit for it.  So all the exe link table entries are processed with CS:offset memory locations.  Then start executing at the location in EXE header, which is a CS:IP address.  Since old EXE format can be hacked and code modified.  PXE compression makes it almost impossible to change.

So it's a bad idea to send source to someone (working on the project) and get an expected hash.  In short it won't happen.
My bad idea is shot down in flames and spirals into the channel.