Executable size affected by module count?

[kris]

Frits van Bommel wrote:
> kris wrote:
> 
>> Walter Bright wrote:
>>
>>> kris wrote:
>>>
>>>> There's no real surprise that this would happen, but it's the actual 
>>>> difference that is cause for a little concern -- it appears that 
>>>> each module consumes 512 bytes minimum. This may actually be a 
>>>> linker thing, but perhaps not?
>>>
>>>
>>>
>>> The way to see what's in an object file is to run obj2asm on it. 
>>> It'll show exactly what's submitted to the linker.
>>>
>>
>> I'm aware of that, thanks.
>>
>> Do you think you could comment on why it might be the linker?
> 
> 
> Suggesting you look at what's submitted to the linker doesn't 
> necessarily imply the linker is the cause. If it receives object files 
> with more data in it (generated by the compiler) and dutifully links 
> them, the output is still bigger ;).

That's right. But I'd already looked at the obj file content, and 
subsequently discounted it :p