[Info-vax] x86-64 VMS executable image sizes and memory requirements ?

[Jan-Erik Söderholm]

Den 2019-12-19 kl. 04:19, skrev John Reagan:
> On Wednesday, December 18, 2019 at 10:09:53 PM UTC-5, Arne Vajhøj wrote:
>> On 12/18/2019 10:05 PM, John Reagan wrote:
>>> On Wednesday, December 18, 2019 at 8:21:55 PM UTC-5, Simon Clubley wrote:
>>>> Now that VSI are starting to get user level programs such as EDT
>>>> running, I was wondering how the x86-64 VMS image sizes and memory
>>>> usage compares to other VMS architectures.
>>>>
>>>> Or is it still too early to get enough data to be meaningful ?
>>
>>> We're building everything NOOPTIMIZE so it isn't worth looking at.
>>>
>>> That said,
>>>
>>> EDTSHR.EXE, Alpha, optimized: 493 blocks on disk, 179,712 bytes of code
>>> EDTSHR.EXE, Itanium, optimized: 724 blocks on disk, 302,960 bytes of code
>>> EDTSHR.EXE, x86, NOT optimized: 589 blocks on disk, 227,120 bytes of code
>>>
>>> and don't ask about x86 optimization.  We haven't even built the LLVM optimizer.  We won't bother until we get native compilers in place.
>>
>> Do you know what it is NOT optimized on Alpha or Itanium?
>>
>> Arne
> 
> As far as I know, we use full optimization on all files in the Alpha and Itanium builds (there might be one or two with explicit /OPT qualifiers, but nothing widespred).
> 
> I just looked at the EDT build on Itanium and it uses /OPTIMIZE with no special settings.  The same build script is used for all 3 architectures.  The x86 compilers just ignore any /OPTIMIZE qualifier.
> 
> And that Alpha image is not one of the EV6 versions from -2L2 but a standard EV4-style code
> 

 From Alpha 8.4-2L2:

$ dir sys$share:edtshr.exe

Directory SYS$COMMON:[SYSLIB]

EDTSHR.EXE;1        470/490       22-MAY-2017 22:49:29.18

Total of 1 file, 470/490 blocks.