9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Building Go/386
Date: Sat, 31 Aug 2013 11:11:32 -0400	[thread overview]
Message-ID: <399e128253888fad1131901a3e8b6672@kw.quanstro.net> (raw)
In-Reply-To: <a5176f54467838c738351aa5f9f143da@proxima.alt.za>

> My gut says this is a Plan 9 problem: something tickled a bug in 8c.
> I hope someone here can diagnose the issue.

sure.  this is not a bug per ce.  it's a limitation of 8c's technique
for registerizing vlongs given the restricted register set of the 386.

8c takes an initial stab at registerizing expressions.  if it needs
more than AX-DI, it can't be compiled without breaking down the
expressions a bit.  spilling is not implemented at this level.

since even ghostscript doesn't get into this state, i'd be interested
in the line of code (and types of the variables) that hits this fatal
condition.

imho the diag() abort() should be replaced with a fatal(), since
-X will give anyone interested a broken process to debug, and leave
anyone not interested alone.

> I needed to modify /sys/include/bio.h as well as
> /sys/src/libbio/^(bgetc.c bputc.c) to get this far in the Go build; I
> have nothing against adding Bgetle2(), Bgetle4(), Bputle2() and
> Bputle4() to libbio, I do wish I had seen that coming.
>
> We do seem to be losing ground to the Go developers, I have a feeling
> that it is going to be hard to catch up.

perhaps chasing the tip isn't going to work.

- erik



  reply	other threads:[~2013-08-31 15:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31 14:36 lucio
2013-08-31 15:11 ` erik quanstrom [this message]
2013-08-31 17:09   ` lucio
2013-08-31 18:12   ` lucio
2013-08-31 21:16     ` erik quanstrom
2013-09-02 18:15       ` Nick Owens
2013-09-02 20:50         ` Rob Pike
2013-09-02 21:51           ` erik quanstrom
2013-09-02 22:08             ` Nick Owens
2013-09-03  0:28               ` erik quanstrom
2013-09-04  6:07         ` lucio
2013-09-07 11:19   ` Anthony Martin
2013-09-07 13:07     ` erik quanstrom

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=399e128253888fad1131901a3e8b6672@kw.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).