On Fri, Aug 16, 2019 at 9:56 AM Richard Miller <9f...@hamnavoe.com> wrote:
> > Do you mean something like BlackIce II (I'm under RV32I)?
>
> Yes, I have tried various soft cores on BlackIce (including
> one of my own design, for fun); also real silicon HiFive-1.
> So far none of these has had an MM
I just went through the patch, aside from minor cosmetic
changes, I think it's ready for inclusion into Go 1.7 if
all.bash passes. The author just has to split it up into
CLs and push to Gerrit for review.
On Sun, May 24, 2015 at 11:55 AM, erik quanstrom
wrote:
> > Uhm I might be mistaken, but I guess [8192]byte is an array, and []byte
> are
> > slices - therefore they are different types.
> >
>
> yes, exactly. i suppose this implies that different size arrays are not
> type compatable
> (yea pasc
On Mar 12, 2015 12:52 PM, "erik quanstrom" wrote:
> so an interesting problem i run into from time to time is separately
computing
> the files added to and deleted from a directory in a shell script. uniq
doesn't
> work for this. certainly one can loop over two lists of files and do
this easily,
On Mar 10, 2015 6:37 PM, "Ryan Gonzalez" wrote:
>
> I meant reading ELF files, not writing them. Last time I tried with
ken-cc, it didn't work.
>
> But I didn't realize Go removed the C compilers. Do you know why?
Because Go runtime is now implemented in Go and assembly, not a combination
of C, G
On Sun, Feb 8, 2015 at 6:42 PM, erik quanstrom
wrote:
> > On Sun, Feb 8, 2015 at 6:27 PM, erik quanstrom
> > wrote:
> > > am i reading the intel docs wrong, or is 6l missing a valid
> instruction?
> > > memmove5: doasm: notfound from=12 to=92 (47)CMOVQNE DX,(DI)> >
> > Go's liblink (which is
On Sun, Feb 8, 2015 at 6:27 PM, erik quanstrom
wrote:
> am i reading the intel docs wrong, or is 6l missing a valid instruction?
>
> memmove5: doasm: notfound from=12 to=92 (47)CMOVQNE DX,(DI)
>
Go's liblink (which is derived from [5869]l) and cmd/6a support this
instruction.
On Mon, Dec 22, 2014 at 7:28 PM, Andrés Domínguez
wrote:
> 2014-12-23 0:39 GMT+01:00 minux :
>
>>
>> On Mon, Dec 22, 2014 at 12:23 PM, Andrés Domínguez
>> wrote:
>>
>>> Has someone run successfully the teg2 port on qemu-system-arm?
>>>
>
On Mon, Dec 22, 2014 at 12:23 PM, Andrés Domínguez
wrote:
> Has someone run successfully the teg2 port on qemu-system-arm?
>
I don't think qemu-system-arm supports the tegra2 platform.
On Fri, Dec 5, 2014 at 12:53 AM, wrote:
> > which also contains a suggested patch
>
> Did you check that the proposed patch actually works?
>
> I see no difference between:
>
> a || b
> and
> a || (a && b) which is (a || a) && (a || b)
>
a || (a && b) is actually just a fancier wa
On Nov 30, 2014 3:10 PM, "Mats Olsson" wrote:
> Just googled and found: https://code.google.com/p/go-wiki/wiki/GoArm
>
> So it seems that it's supported.
go on arm only supports Linux, Freebsd, Netbsd, nacl and Darwin
(unofficial).
plan 9 is not on the list (yet).
On Fri, Nov 28, 2014 at 11:42 PM, arisawa wrote:
> rc(1) says:
>
> rfork [nNeEsfFm]
>Become a new process group using rfork(flags) where
>flags is composed of the bitwise OR of the rfork flags
>specified by the option letters (see fork(2)).
On Fri, Nov 28, 2014 at 7:54 PM, Ryan Gonzalez wrote:
> I Google'd it, but I didn't find anything. Does it build?
If you stub out a lot of unsupported stuff from lib9, it should build and work.
For example, Go (gc) toolchain uses a modified lib9 and libbio on Windows,
and it's working fine. (Must
On Wed, Nov 19, 2014 at 2:22 PM, Skip Tavakkolian
wrote:
> they're well made, priced right, and fast (e.g. compiling Go on linux on rpi
> is *very* slow when compared with older odroid-u2 with the same config).
the problem is that samsung doesn't publish the datasheet for its processors
without ND
On Nov 17, 2014 9:29 PM, "Bakul Shah" wrote:
> I don't know about Go (the Go guys are probably already
> suffering from a massive VCS fatigue), but if you want to play
> with this idea, there is venti! Vac can take a previous score
> to do incremental archiving. If you add sepcial blocks that
> st
On Nov 13, 2014 2:25 PM, "Skip Tavakkolian"
wrote:
> - in order to run go built for plan9/386 on 9vx, presumably go should be
built without support for SSE2. is there a way to avoid this?
set GO386 to 387 before running all.rc
On Fri, Oct 17, 2014 at 4:00 PM, Yoann Padioleau wrote:
>
> 0:int - x was not enough for those balancing(?) and promoting thing?
>
It's enough for type promotion, but you changed the semantics of the
program.
17 matches
Mail list logo
