On Thu, 26 May 2011 11:34:29 -0400, erik quanstrom wrote:
... it to high gives me a warning that there are to many procs for
devproc...
this is a bug in the warning message.
; diffy -c devproc.c
...
+ #define SLOTBITS 23 /* number of bits in the slot */
+ #define SLOTMASK ((1<<SLOTBITS)-1 << QSHIFT)
...
Thanks, I have added this patch to my ebuilds.
The system still crashes with very large numbers of procs (I think it
is overrunning the static definition of libvx32/proc.c vxproc
*procs[VXPROCSMAX]), but for now spawning 64 tasks is ok for
development, but all the tests are shooting for 512. It would be nice
to get all the systems running consistently. Any suggestions are
greatly appreciated.
EBo --
