[comp.sys.ncr] Dimension table overflow

nigel@cmsfl@labtam.oz (Nigel Harwood) (01/13/90)

I was recently loading some new communications s/w onto one of our
Tower 32/650s for the first time.  When the update had been loaded
and the kernel was being relinked etc a message came up saying that the
dimension table had overflowed processing a particular header file
(I think it was sys/io.h).

This system has quite a lot of comms software loaded so I expect
this has something to do with it.

Anyway I increased the -Sd,2000 in the CFLAGS to -Sd,3000 and tried
again.  It worked okay.

Any comments on this ?  i.e. is it an indication that we are putting
too much into the kernel or is it just a matter of 2000 being the
normal default for most users.

Also I would not expect the 2000 to 3000 change to have made any
difference to the resultant kernel i.e. size wise, would it ?

-- 
<<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>
<< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >>
<< Phone: +61 3 829 6090      E-mail: nigel%cmsfl@labtam.oz.au >>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

wescott@Columbia.NCR.COM (Mike Wescott) (01/16/90)

In article <324@cmsfl> nigel@cmsfl@labtam.oz (Nigel Harwood) writes:
> Anyway I increased the -Sd,2000 in the CFLAGS to -Sd,3000 and tried
> again.  It worked okay.

> Any comments on this ?  i.e. is it an indication that we are putting
> too much into the kernel or is it just a matter of 2000 being the
> normal default for most users.

No. Just an indication that the compiler was not set up to handle
such a large program as the default.

> Also I would not expect the 2000 to 3000 change to have made any
> difference to the resultant kernel i.e. size wise, would it ?

No effect on kernel size, just the compiler.

--
	-Mike Wescott
	 mike.wescott@ncrcae.Columbia.NCR.COM