Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice blink question
Message-ID: <1382@sas.UUCP>
Date: 18 Dec 89 15:47:28 GMT
References: <596@cameron.cs.duke.edu>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 26

In article <596@cameron.cs.duke.edu> amr@dukee.egr.duke.edu (Anthony M. Richardson) writes:
>...but the
>blink.readme file says to compile all user routines with the -ml option.  
>Anyone know what this does? I couldn't find it documented anywhere.

According to Steve Krueger, who implemented the LIB option on BLINK,
the -ml compiler option does the following:

1.  If the __saveds keyword is present on the function definition
    (or if the -y compiler option is used, which does the same
    thing) the global data pointer is loaded into A4 from the
    appropriate offset off of the library base (A6).

2.  It preserves A6 across calls to other resident libraries.

If you are going to use global data in the function, you must
compile with -y or declare the function with __saveds to get
addressability.


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