Re: [go-nuts] gccgo problem compiling go from source

by specific updates in the generator scripts (in >> unix/mkpost.go). There was also a problem with Statfs_t struct. >> >> 4. I am not an expert wrt cgo, but if I understand correctly, through the >> use of the cgo tool that is distributed with gccgo and knows ppc, we

Re: [go-nuts] gccgo problem compiling go from source

Hi Mirza, On Thu, Nov 5, 2020 at 3:18 PM 'Mirza Krak' via golang-nuts < golang-nuts@googlegroups.com> wrote: > On Tuesday, October 20, 2020 at 9:52:17 AM UTC+2 hugo.c...@essensium.com > wrote: > >> 1. Build the gccgo cross-toolchain with Buildroot: Buildroot currently >> builds a toolchain by fir

Re: [go-nuts] gccgo problem compiling go from source

y, through the use of the cgo tool that is distributed with gccgo and knows ppc, we avoided small problems with cgo invocation. 5. I believe (all) the patches we did to the generator script 'mkall.go' are superseded by the upstream patches. Regards, Hugo On Fri, Oct 23, 2020 at 10

Re: [go-nuts] gccgo problem compiling go from source

Hi Gerrit, Yes, that was the plan, but it looks like powerpc support was already added to the sys/unix package last week. When we were working on this package we first had several subtle and difficult to debug problems. As part of debugging, we developed unit tests for validation of some of the

Re: [go-nuts] gccgo problem compiling go from source

Hi Gerrit, If I understand correctly, I believe you try to cross-compile Go applications to the PowerPC e500 architecture and as a first step you are porting Go to this architecture. We recently ported Go applications such as Docker and its tools to architectures not supported by upstream Go, but

Re: [go-nuts] Port to powerpc 440fpu

look further into the underlying problem. Hugo On Thu, Jul 9, 2020 at 10:08 AM Hugo Cornelis wrote: > > > On Fri, Jul 3, 2020 at 9:36 PM Ian Lance Taylor wrote: > >> That looks like the process is writing to a pipe that nothing is reading >> from. >> > >

Re: [go-nuts] Port to powerpc 440fpu

On Fri, Jul 3, 2020 at 9:36 PM Ian Lance Taylor wrote: > That looks like the process is writing to a pipe that nothing is reading > from. > Yes, that is correct. The question is: why doesn't the reader read from the pipe? And why does it suddenly start reading when the Docker daemon process is

Re: [go-nuts] Port to powerpc 440fpu

Thanks for your answer. On Mon, Jun 29, 2020 at 9:10 PM Ian Lance Taylor wrote: > Thanks for the background. > > Earlier I suggested looking at the output of "strace -f" for the > programs that fail. Does that show anything of interest? > What follows is the analysis of one strace (strace -fv

Re: [go-nuts] Goroutines count and id

ineheader(gp *g) { nameLength := atomic.LoadUint32(&gp.nameLength) if nameLength != 0 { - print("goroutine ", gp.goid, " '") + print("goroutine, name: ", gp.goid, " '") gwrite(gp.name[0:nameLength]) print("' [", status)

Re: [go-nuts] Port to powerpc 440fpu

n this for several weeks now, any help would be greatly appreciated. Thanks! Hugo On Fri, Jun 19, 2020 at 3:33 AM Ian Lance Taylor wrote: > On Thu, Jun 18, 2020 at 1:17 PM Hugo Cornelis > wrote: > > > > Does anyone have experience with porting go applications to the powerpc

[go-nuts] Port to powerpc 440fpu

Hi all, Does anyone have experience with porting go applications to the powerpc 440fpu 32 bit. We have a team that is porting the Docker tool suite to a device that uses this CPU, we generated the system call bindings and compiled the Docker tool suite without much problems. Most of Docker s