On Tue, Jan 11, 2011 at 3:45 PM, Federico G. Benavento
wrote:
> it's not fcnlt's fault, ape replaces your sockfd with a pipe
> when you do listen(), you could call fcntl again after the
> listen() call...
>
> all this is usually combined with select() which in turns does
> more magic behind the sc
On Tue, Jan 11, 2011 at 4:06 PM, Fernan Bolando wrote:
> On Tue, Jan 11, 2011 at 3:45 PM, Federico G. Benavento
> wrote:
>> it's not fcnlt's fault, ape replaces your sockfd with a pipe
>> when you do listen(), you could call fcntl again after the
>> listen() call...
>>
>> all this is usually comb
Is it possible to take a look at what you did? I can't be considered
expert, just interested and may be I can try to contribute.
Cheers
-Peter
2011/1/10 Artem Novikov :
> I want to build Plan9 from scratch under Windows/*NIX.
> I built working (seems :) toolchain (yacc, 8a, 8c, 8l) under Windows
fcntl() didn't fail, it has to do with listen()'s implementation
which creates a pipe, dups and forks... but the new fd
doesn't have O_NONBLOCK set.
check /sys/src/ape/lib/bsd/listen.c
and yes it's an incompatibility
On Tue, Jan 11, 2011 at 5:18 AM, Fernan Bolando wrote:
> On Tue, Jan 11, 2011
On 11 янв, 02:01, nicklafo...@gmail.com (Nick LaForge) wrote:
> I'm curious: do you plan on executing the output of 8c and 8l in an
> environment as strange as one the you are building in? You could try
> building only programs and then try executing those, i.e., by using
> one of
>
> http://www.c
Sorry, I wanted to say half a ms.
I also see 100us on another pc.
On Tue Jan 11 02:55:42 EST 2011, skip.tavakkol...@gmail.com wrote:
> hell-o.go is like hello.go but uses println. 8.hell-o works properly
> on a plan9 cpu. but it faults when running on 9vx. i built vx32 --
> including 9vx -- on a linux/x86-64 from sources in the last couple of
> days.
>
> % 8.hel
2011/1/11 erik quanstrom :
> On Tue Jan 11 02:55:42 EST 2011, skip.tavakkol...@gmail.com wrote:
>> hell-o.go is like hello.go but uses println. 8.hell-o works properly
>> on a plan9 cpu. but it faults when running on 9vx. i built vx32 --
>> including 9vx -- on a linux/x86-64 from sources in the las
can you do a ratrace for me?
ron
i suspect go is using segment register(s) to implement extern register,
and that isn't expected (or perhaps even supported) by 9vx.
just a guess.
I'm typing from my phone so I don't have go sources in front of me,
but 0xdfffefc0 looks like the address I used for per thread G and M
structs - just bellow struct Tos.
Andrey and I also tried running on a 32-bit 9vx with the same effect.
Is 9vx using a different memory layout than Plan 9?
On T
On Tue, Jan 11, 2011 at 9:03 AM, Charles Forsyth wrote:
> i suspect go is using segment register(s) to implement extern register,
> and that isn't expected (or perhaps even supported) by 9vx.
> just a guess.
>
>
I did not realize this was currently supported by Plan 9 ... maybe I
didn't get the m
Pavel Zholkover once said:
> I'm typing from my phone so I don't have go sources in front of me,
> but 0xdfffefc0 looks like the address I used for per thread G and M
> structs - just bellow struct Tos.
>
> Andrey and I also tried running on a 32-bit 9vx with the same effect.
>
> Is 9vx using a
Anthony Martin once said:
> The Tos structure is bigger on 64-bit 9vx so the references
> to GS will need a different offset. You'll have to change
> both src/8l/pass.c:/^patch and the runtime.
I forgot to mention that on 9vx, USTKTOP is at 0x1000.
Anthony
I did the runtime port a few month ago, now waiting for
http://codereview.appspot.com/3816043/ to get reviewed and
committed... there are still a bunch of things missing like linking
with symbols, os.ForkExec and environment variables at early runtime.
time package is also not ready, so I can't ru
On Tue, Jan 11, 2011 at 10:55 AM, Anthony Martin wrote:
> Pavel Zholkover once said:
>> I'm typing from my phone so I don't have go sources in front of me,
>> but 0xdfffefc0 looks like the address I used for per thread G and M
>> structs - just bellow struct Tos.
>>
>> Andrey and I also tried run
>I did not realize this was currently supported by Plan 9 ... maybe I
>didn't get the memo?
go's 8c/8l convert extern register to references off a segment register,
although the implementation of extern register isn't general enough for plan 9
kernel use;
it's just enough for go. it sounds as tho
17 matches
Mail list logo
