Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!gatech!udel!rminnich
From: rminnich@udel.EDU (Ron Minnich)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Another question on the 80286- er, 68000 memory models
Message-ID: <2653@louie.udel.EDU>
Date: 20 May 88 15:22:36 GMT
References: <8805182223.AA20918@cory.Berkeley.EDU>
Reply-To: rminnich@udel.EDU (Ron Minnich)
Organization: University of Delaware
Lines: 26

In article <8805182223.AA20918@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>	I.E. *ANY* run-time (shared) library cannot assume that A4 will
>point to it's data when it is called, period... it's one of those things
That is not the sort of thing i am worried about. internet.device
munges a4, for example. But what about functional parameters? 
>and restore it before returning.  Small-code doesn't enter in the picture
>at all because it uses the relative(pc) format which doesn't depend on
>any (standard) register.
ah, so the lattice -r1 switch is useless for the amiga? Sounds like
if you use -r1, then you should not use libraries? So now the
problem is reduced to dealing with the medium and  large models,
and the sort of falls-between-the-holes type questions which 
i am not 100% sure the rules you cite will always address. At least,
they haven't on xenix kernels ...
   No, i have no problem with your discussion. I knew all that 
stuff anyway. But the fun i am having with xenix kernel hacking
has me a little worried, even though i have not been burned yet ...
For example, i put a pointer into a structure. Now if i am
in the small data mode, then maybe what gets put in is 16 bits. 
Then i go to the library which is large model, ... bang!
   Anyway, i will try to work up a more concrete example and see
if this scenario is possible. I sure hope not.And i have not
seen it yet, or been burned by it, but it bothers me somehow.

-- 
ron (rminnich@udel.edu)