🚀 go-pugleaf

On Fri, 12 Nov 1993, Michael J Knudsen +1 708 713 5134 wrote:

> >        I was going to be doing work w/ hundreds of tiny modules that
> >would be linking and unlinking on the fly, so even when all was in memory,
> >the 070 would be page faulting continuously.  The 340 is fast enough to
>
> Is this page faulting for real?  I guess it is, if all those
> modules each have their own process space.  But I thought the 070
> just ran a full flat-out address space and didn't bother with all
> that L2 mapping stuff.

     Yeah, each would have its own space.  W/ only 8 MMU translators on
the 070 at a time, maps would be falling out all of the time :).  You're
right, under OSK, the 070 is in flat map mode -- I'm just messing w/ other
ideas.

> I remember Kev P had to increase the delay in the MM/1 boot ROMs
> too.  And I think he changed Break's effects too.  He's probably
> reading this List and will get onto a fix.

     Cool!  I may need to fix my Disto ERPOM burner for my MM1! :)

> What's the problem with the libs and linker?  I know the linker

     All of the OS9 defs are stored in a library, and all of the standard
libraries use them, so when the linker goes to work, it not only has to
bind the std libraries to your code, but it also has to bind the OS9 defs
to the std libraries!  This is fine if you are changing the std defs
regularly, but we aren't!  Ultra C fixes this (I think) by letting you
do that linking once and for all before hand...

> I'd be much more interested in the 340 upgrade if I could compile
> the improved 020-style C code.

     What's wrong w/ gcc?  Or are you refering to 020 specific additions
to the C langauge?