From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e9f27bbe0678fdfc X-Google-Attributes: gid103376,public From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) Subject: Re: huge executable?? Date: 2000/05/16 Message-ID: #1/1 X-Deja-AN: 624179662 References: <391E09C3.FA04871E@mailandnews.com> <392184A8.C9256A53@maths.unine.ch> X-Trace: news.decus.org 958500620 1362 KILGALLEN [216.44.122.34] Organization: LJK Software Reply-To: Kilgallen@eisner.decus.org.nospam Newsgroups: comp.lang.ada Date: 2000-05-16T00:00:00+00:00 List-Id: In article <392184A8.C9256A53@maths.unine.ch>, Gautier writes: > Robert A Duff : > >> > What about paging? > > Larry Kilgallen: > >> "Code" that never gets paged in (for execution) has no need to be >> paged out. > > But you can have code that is paged in without being ever executed - > it could suffice it is at a small distance from executed code, in the > same memory block. Couldn't it ?... Absolutely. But in addition to the code under discussion that can never be called, the code that is never used also includes those codepaths never traversed that happen to be close to codepaths that are used with this particular set of input data. That seems to me much more likely to be in the same memory block.