[go-nuts] Right way to convert c char to golang bytes

I want to convert *C.uchar to bytes slice. I've tried C.GoBytes. But, C.GoBytes is not giving the exact result. Because, it is truncating at zero. for example. If I have *C.uchar like this, [1,3,5,0,2,4,5]. I expect my go bytes like this [1,3,5,0,2,4,5] But, I get [1,3,5,0,0,0] If I use C.Gob

[go-nuts] mdiff: Multi Text Differ impremented by Golang

Hi. i'm engeneer in japan. I write any programs as a hobby each days. Today, I introduce new diff tool made me. features are.. - compare different on multi tab - difference text is colored - can search words - can apply difference to target file - multi platform support by golang https://

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

I thought HPE Nonstop uses the Itanium processor (X64, not X86-64, it's completely unrelated to the common desktop CPU). You'd need to create a new code generator for that platform, and given that it's a VLIW processor that would be a major research project. Endianness is the least of your problems

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

On Fri, Jun 5, 2020 at 3:46 PM Randall Becker wrote: > > That's actually what I figured. So where do I look to add nsx to the > toolchain? You'll have to fix the linker to generate whatever nsx expects. You'll have to add code to support nsx in the runtime and syscall packages. Pick which suppo

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

That's actually what I figured. So where do I look to add nsx to the toolchain? On Friday, 5 June 2020 17:03:11 UTC-4, Ian Lance Taylor wrote: > > On Fri, Jun 5, 2020 at 12:49 PM Randall Becker > wrote: > > > > Some progress. I've managed to build 1.14.4 using the Windows GO > implementation.

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

On Fri, Jun 5, 2020 at 12:49 PM Randall Becker wrote: > > Some progress. I've managed to build 1.14.4 using the Windows GO > implementation. The trouble I was having was using cygwin64. After figuring > that part out... > > I checked out a new branch from release_go1.14 named nonstop_port > > Th

Re: [go-nuts] Trying to port Go to HPE NonStop x86 - Need some guidance

Some progress. I've managed to build 1.14.4 using the Windows GO implementation. The trouble I was having was using cygwin64. After figuring that part out... I checked out a new branch from release_go1.14 named nonstop_port Then ran GOARCH=amd64 GOOS=nsx bootstrap.bash which failed because I a

[go-nuts] Re: Why are escape analysis results of these two programs different?

I've dug a little bit deeper into this. The root cause is https://github.com/golang/go/blob/master/src/cmd/compile/internal/gc/escape.go#L725 here, this line only pass when dst.Op == ODOTPTR rather than ODOTPTR || ODOT. I have a very simple patch to solve this, but I don't know whether this i

[go-nuts] Why are escape analysis results of these two programs different?

https://play.golang.org/p/PL0FCLCv3qU You'll find that x1() and x2() are different. Then I run `go tool compile -m -m`: ``` unsafestr.go:11:11: make([]byte, 12) escapes to heap: unsafestr.go:11:11: flow: b = &{storage for make([]byte, 12)}: unsafestr.go:11:11: from make([]byte, 12) (spill)