9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Martin <ality@pbrane.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9 go output faults on 9vx but ok on cpu
Date: Wed, 12 Jan 2011 14:31:02 -0800	[thread overview]
Message-ID: <20110112223102.GA5183@dinah> (raw)
In-Reply-To: <AANLkTimj+nRcVxTViHT7snZrzQx2hTf+7YmH+mEySVfd@mail.gmail.com>

ron minnich <rminnich@gmail.com> once said:
> are you saying change 8l so that it creates code that works on 9vx in
> the special case that it runs on a 64-bit system? Then we're going to
> need to make 8l aware of way too much stuff.

I'm talking about Go's linker. In the Go runtime, the G and M
pointers need to be in a per-process storage area. On Plan 9,
this is the stack. Right now, the offset of the pointers is
hard-coded in the linker to be just before the Tos structure.
The problem is that the value that was chosen is not correct
when running on 9vx because the top of the stack is is at
0x10000000 instead of 0xdffff000 (as it is on native Plan 9).

I think that the Go 8l should not hard-code this value but,
instead, discover it somehow ... though I'm not sure how.

  Anthony



  reply	other threads:[~2011-01-12 22:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  7:54 Skip Tavakkolian
2011-01-11 14:11 ` erik quanstrom
2011-01-11 15:06   ` Devon H. O'Dell
2011-01-11 17:03   ` Charles Forsyth
2011-01-11 17:51     ` ron minnich
2011-01-11 19:35       ` Pavel Zholkover
2011-01-11 23:58       ` Charles Forsyth
2011-01-11 16:25 ` ron minnich
2011-01-12  8:32   ` Skip Tavakkolian
2011-01-12 16:12     ` andrey mirtchovski
2011-01-12 22:03       ` ron minnich
2011-01-13  5:54     ` ron minnich
2011-01-14 17:32       ` Pavel Zholkover
2011-01-15  2:00         ` Anthony Martin
2011-01-15  9:47           ` Pavel Zholkover
2011-01-15  9:01         ` kokamoto
2011-01-15  9:19           ` Pavel Zholkover
2011-01-15  9:30           ` lucio
2011-01-15  9:58             ` Pavel Zholkover
2011-01-15 10:29               ` lucio
2011-01-15 10:40               ` lucio
2011-01-15 11:25                 ` Pavel Zholkover
2011-01-16  1:51                   ` kokamoto
2011-01-16  2:04                     ` kokamoto
2011-01-16  6:21                       ` kokamoto
2011-01-17 12:03                         ` kokamoto
2011-01-17 15:20                         ` [9fans] how to make hardware work? sergey.kish
2011-01-16  2:06                     ` [9fans] plan9 go output faults on 9vx but ok on cpu Skip Tavakkolian
2011-01-11 17:03 ` Pavel Zholkover
2011-01-11 18:55   ` Anthony Martin
2011-01-11 19:06     ` Anthony Martin
2011-01-11 22:58     ` ron minnich
2011-01-12 22:31       ` Anthony Martin [this message]
2011-01-12 22:36         ` erik quanstrom
2011-01-12 23:28           ` Pavel Zholkover
2011-01-12 23:29         ` Charles Forsyth

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=20110112223102.GA5183@dinah \
    --to=ality@pbrane.org \
    --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).