From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go
Date: Wed, 11 Nov 2009 23:46:32 -0600 [thread overview]
Message-ID: <30414357-531B-451C-A4D1-46DE5D33295A@corpus-callosum.com> (raw)
In-Reply-To: <dd6fe68a0911112125p13070ff2u5b1d3e2223e8826c@mail.gmail.com>
now now...
On Nov 11, 2009, at 11:25 PM, Russ Cox wrote:
> On Wed, Nov 11, 2009 at 9:08 PM, andrey mirtchovski
> <mirtchovski@gmail.com> wrote:
>
>> $ export GOMAXPROCS=4000000000
>> $ 6g sieve.go ; 6l -o sieve sieve.6
>> $ ./sieve
>> throw: all goroutines are asleep - deadlock!
>
> That's not fair! The minimal version of this is:
>
> GOMAXPROCS=2147483648 sieve
>
> 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=`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
next prev parent reply other threads:[~2009-11-12 5:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 6:00 Russ Cox
2009-11-11 6:33 ` Anant Narayanan
2009-11-11 6:47 ` Skip Tavakkolian
2009-11-11 11:27 ` Eris Discordia
[not found] ` <D67AC32CFE1076880E2CDDD5@192.168.1.2>
2009-11-11 16:25 ` John Waters
2009-11-11 17:23 ` roger peppe
2009-11-11 7:25 ` Roman Shaposhnik
2009-11-11 17:23 ` Russ Cox
2009-11-12 5:08 ` andrey mirtchovski
2009-11-12 5:25 ` Russ Cox
2009-11-12 5:46 ` Jeff Sickel [this message]
2009-11-12 6:39 ` Russ Cox
2009-11-12 16:37 ` Michaelian Ennis
2009-11-12 17:09 ` AngryDude
2009-11-12 4:31 Nick LaForge
2009-11-12 5:27 ` Roman Shaposhnik
2009-11-12 15:28 ` Devon H. O'Dell
2009-11-12 20:51 ` Nick LaForge
[not found] <<9ab217670911120728q137ac2c1j4f11d9a1d8b2ded5@mail.gmail.com>
2009-11-12 16:37 ` erik quanstrom
2009-11-12 16:59 ` Devon H. O'Dell
2009-11-12 18:49 ` Roman Shaposhnik
[not found] <<9ab217670911120859u25b8f6f0m57cad5c126d75d65@mail.gmail.com>
2009-11-12 17:13 ` erik quanstrom
2009-11-12 17:29 ` LiteStar numnums
2009-11-12 18:40 ` Tharaneedharan Vilwanathan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30414357-531B-451C-A4D1-46DE5D33295A@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).