From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) From: Jeff Sickel In-Reply-To: Date: Wed, 11 Nov 2009 23:46:32 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <30414357-531B-451C-A4D1-46DE5D33295A@corpus-callosum.com> References: <14ec7b180911112108i104fca15u9503362cfc30769f@mail.gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Go Topicbox-Message-UUID: 99c4f64a-ead5-11e9-9d60-3106f5b1d025 now now... On Nov 11, 2009, at 11:25 PM, Russ Cox wrote: > On Wed, Nov 11, 2009 at 9:08 PM, andrey mirtchovski > wrote: >=20 >> $ export GOMAXPROCS=3D4000000000 >> $ 6g sieve.go ; 6l -o sieve sieve.6 >> $ ./sieve >> throw: all goroutines are asleep - deadlock! >=20 > That's not fair! The minimal version of this is: >=20 > GOMAXPROCS=3D2147483648 sieve >=20 > You can guess what's going on. In this day and age of so much 64bit goodness and so many multi-cored = systems available, shouldn't it be something more like: GOMAXPROCS=3D`hoc -e '2^32'` sieve let alone `hoc -e '2^64' Then again, if my hoc were arbitrarily clean enough, it should return a = valid result for: % hoc -e '2^2^2^2^2' hoc: exponentiation result out of range in -e near line 2 (the Plan 9 error code is 'hoc: exponentiation result out of range near = line 2') I want my BigEnough numbers for those times when enough just isn't = enough. Hrm... maybe it's time for a hoc.go or an apc.go = implementation. -jas