Mark Roulo (nothanks.delete@this.xxx.com) on May 10, 2017 4:12 pm wrote:
> anon (anon.delete@this.anon.com) on May 10, 2017 4:30 am wrote:
> > Brett (ggtgp.delete@this.yahoo.com) on May 9, 2017 11:33 pm wrote:
> > > anon (anon.delete@this.anon.com) on May 8, 2017 11:24 am wrote:
> > > > Brett (ggtgp.delete@this.yahoo.com) on May 8, 2017 2:48 am wrote:
> > > > > Clearly I should have refreshed my memory by reading the manual. ;)
> > > > > 256 megabytes is not big enough for UNIX calls, and you only get the negative
> > > > > half of that for OS calls, the other half for your app calls.
> > > > >
> > > >
> > > > What do you mean by UNIX call and OS call, and what negative half?
> > >
> > > Memory layout
> >
> > Still not sure what you mean.
>
> I think Brett may believe that calls to the operating system are
> made via unconditional branch instructions. His concern is that the
> OS code to which one will be branching is more than 256 MB away in
> user process space.

I spent 20 years writing C to game consoles that had no real OS. Never paid attention to
OS calls as there was nothing to optimize there that could matter.
So I will just punt while I am behind, maybe next week I will come back and fix my screw ups.