From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
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 00:32:36 -0800 [thread overview]
Message-ID: <AANLkTi=tnaw5b7PMWd0sTP6CGG1fROvBatFgZPasiHCW@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim0dPgQaqg6+E9oF6xMfPeFEg8QuT8q4cFf8yfw@mail.gmail.com>
On Tue, Jan 11, 2011 at 8:25 AM, ron minnich <rminnich@gmail.com> wrote:
> can you do a ratrace for me?
>
> ron
>
>
i'll have to rebuild using the vx32 branch on your bitbucket. is it up
to date with the changes to compile on linux/x86-64?
here it is on acid:
% acid 8.hell-o
8.hell-o:386 plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/386
no symbol information
acid: new()
299: exception 576 0x7045 MOVL AX,0x18cfc
<stdin>:2: (error) main used but not set
acid: asm(*PC-32)
0x7025 0x00007025 CALLL 0x3b9a:0xca00ba3b
0x702c 0x0000702c MULL AX,DX
0x702e 0x0000702e ADDL CX,DX
0x7030 0x00007030 JMP 0x7002
0x7032 0x00007032 MOVL DX,CX
0x7034 0x00007034 IMULL CX,$0x3e8,CX
0x703a 0x0000703a MOVL $0x3e8,DX
0x703f 0x0000703f MULL AX,DX
0x7041 0x00007041 ADDL CX,DX
0x7043 0x00007043 JMP 0x6fe2
0x7045 0x00007045 MOVL AX,0x18cfc
0x704b 0x0000704b MOVL SP,SI
0x704d 0x0000704d SUBL $0x8,SP
0x7050 0x00007050 MOVL SP,DI
0x7052 0x00007052 MOVL AX,CX
0x7054 0x00007054 SUBL SI,CX
0x7056 0x00007056 CLD
0x7057 0x00007057 REP MOVSB (SI),(DI)
0x7059 0x00007059 SUBL SI,DI
0x705b 0x0000705b MOVL 0x0(SP),CX
0x705e 0x0000705e LEAL 0x4(SP),BP
0x7062 0x00007062 ADDL DI,0x0(BP)
0x7065 0x00007065 ADDL $0x4,BP
0x7068 0x00007068 LOOP 0x7062
0x706a 0x0000706a JMP 0x1092
0x706f 0x0000706f MOVL 0xdfffefc0,CX
0x7075 0x00007075 CMPL 0x0(CX),SP
0x7077 0x00007077 JHI 0x7085
0x7079 0x00007079 XORL DX,DX
0x707b 0x0000707b MOVL $0x8,AX
acid:
next prev parent reply other threads:[~2011-01-12 8:32 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 [this message]
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
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='AANLkTi=tnaw5b7PMWd0sTP6CGG1fROvBatFgZPasiHCW@mail.gmail.com' \
--to=skip.tavakkolian@gmail.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).