Article View: comp.lang.modula2
Article #1303FST executable sizes
From: Brian M McNamara
Date: Sun, 28 Oct 1990 14:59
Date: Sun, 28 Oct 1990 14:59
9 lines
936 bytes
936 bytes
The FST linker (I don't think the version even matters) seems to carry a lot of overhead from SYSTEM an FileSystem, as well as including all procedures from any DefMod you may have called. However, when using m2link (i.e. not in the interactive editor) you can specify /o to optimize the executable program. I often see sizes of 3K or 4K when doing this. It is slow to optimize, but as mentioned...it is a hell of a product for shareware. Brian
Technical Details
Message-ID:
<43003@eerie.acsu.Buffalo.EDU>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!ub!ubvmsa.cc.buffalo.edu!v056ped5Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!ub!ubvmsa.cc.buffalo.edu!v056ped5 From: v056ped5@ubvmsa.cc.buffalo.edu (Brian M McNamara) Newsgroups: comp.lang.modula2 Subject: FST executable sizes Message-ID: <43003@eerie.acsu.Buffalo.EDU> Date: 28 Oct 90 14:59:32 GMT Sender: news@acsu.Buffalo.EDU Reply-To: v056ped5@ubvmsa.cc.buffalo.edu Organization: University at Buffalo Lines: 9 Nntp-Posting-Host: ubvmsa.cc.buffalo.edu News-Software: VAX/VMS VNEWS 1.3-4.3