🚀 go-pugleaf

	When attempting to route a large (40 modules) design with
	magic, we are getting some unexplained behavior. The
	router apparently does the channel definitions, then
	begins the assignments; it prints out many pound signs
	('#').  Magic then goes off into a mode wherein it prints
	out no more information, but gets more and more memory,
	until the operating system runs out of swap space.

	I would presume that this problem is too large for magic,
	but it successfully routes 'half' of the problem in much
	less time with much less memory.  Anybody out there have
	some hints as to what may be going on?  Is there a bug
	in magic that we should know about?

	Thanks,
	Wayne E. Winder