Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mailrus!uwm.edu!cs.utexas.edu!rutgers!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Lattice BLINK & ALV's
Message-ID: <1395@sas.UUCP>
Date: 20 Dec 89 21:41:43 GMT
References: <301@egrunix.UUCP>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 21

In article <301@egrunix.UUCP> cogswell@unix.secs.oakland.edu (Dan Cogswell) writes:
>	(a)  What *IS* and Automatic Link Vector (ALV)?
It is desirable to use 16-bit references to jump to routines in your
code (BSR instead of JSR) since it is smaller and faster.  However, sometimes
you have more than 64k of code;  this makes it impossible to jump directly to
the code with a 16-bit offset.  BLINK is fixing up your code so it will
work anyway.  It sticks a 16-bit branch into your code which takes you to
a 32-bit jump - kind of a one-statement inline function.  Using this 
technique, you get the benefits of 16-bit offsets for 99% of your program
and you can still address more than 64k of code.

Blink is merely warning you about what it did.  You don't need to worry 
about the messages, they are merely informative.


  *****
=*|_o_o|\\=====Doug Walker, Software Distiller=======================
 *|. o.| ||
  | o  |//     "READY!   FIRE!   AIM!   (Software under development!)
  ======
usenet: ...mcnc!rti!sas!walker   plink: dwalker  bix: djwalker