Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC840302); site boring.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!boring!guido From: guido@boring.UUCP Newsgroups: net.micro.mac Subject: Re: PD Modula2 Loader: How it works! Message-ID: <6569@boring.UUCP> Date: Thu, 8-Aug-85 11:44:15 EDT Article-I.D.: boring.6569 Posted: Thu Aug 8 11:44:15 1985 Date-Received: Sun, 11-Aug-85 07:22:34 EDT References: <87@ssc-vax.UUCP> Reply-To: guido@mcvax.UUCP (Guido van Rossum) Distribution: net Organization: "Stamp Out BASIC" Committee, CWI, Amsterdam Lines: 13 Apparently-To: rnews@mcvax.LOCAL In article <87@ssc-vax.UUCP> keith@ssc-vax.UUCP (Keith Nemitz) writes: >The compiler generates object code that includes the use of absolute >memory references. Apparently the loader 'fixes' the code in memory >and changes any absolute references to reflect the position in >memory. Woeful tidings to anyone who hopes to generate CODE >segments from the object code files produced by the compiler. Well, it's not impossible. The SUMacC C compiler (a cross-compiler running on VAXen) also generates absolute memory references, but its run-time start-up routine relocates the program as it is loaded (with some help from a table generated by the SUMacC rmaker). Guido van Rossum, CWI, Amsterdam (guido@mcvax.UUCP)