Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.16 $; site pbear.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!whuxl!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!timeinc!phri!pesnta!amd!amdcad!decwrl!decvax!yale!pbear!peterb
From: peterb@pbear.UUCP
Newsgroups: net.arch
Subject: Re: Re: 16032 code generation
Message-ID: <600004@pbear.UUCP>
Date: Fri, 28-Jun-85 20:39:00 EDT
Article-I.D.: pbear.600004
Posted: Fri Jun 28 20:39:00 1985
Date-Received: Wed, 3-Jul-85 09:25:26 EDT
References: <2358@sun.UUCP>
Lines: 17
Nf-ID: #R:sun:-235800:pbear:600004:000:822
Nf-From: pbear!peterb    Jun 28 18:39:00 1985



	Well I know that on my little PC/IX system, "binding" is done for
some of the libraries. This will link the code together and leave the
unresolved for later. This is possible since all jumps anc calls are
pc-relative. Globals/externs are the only tags classes that can no be
resolved at that time. It sure does speed link time...

	Peter Barada
	{ihnp4!inmet|{harvard|cca}!ima}!pbear!peterb

Ps - The 8086 small model is a snap to produce fast code for, all you have
to do is keep in mind what registers are usable for indexinc, and work
around the special caseds for mul/div. The rest is pretty straight forward.
In fact I am working on a small model pascalish language that can nest
procecedures and functions, and the code generation is very straight
forward. I will post times for c/pl0 comparisons at a later date.