Re: [go-nuts] Questions Regarding Go 1.15 Dwarf generation

he 1.15 release the linker wasn't completely > converted to a new internal representation. > > HTH > > Than > > > > > On Tue, Feb 23, 2021 at 12:29 PM Mahdi Hosseini > wrote: > >> Thanks for your reply. >> Actually yes, I am looking at the dwarfG

Re: [go-nuts] Questions Regarding Go 1.15 Dwarf generation

Thanks for your reply. Actually yes, I am looking at the dwarfGenerateDebugSyms function in dwarf.go in cmd/lin/internal/ld trying to understand how and when CUs are being generated and then added to dwarfp2 specially the header and length of each CU. R, Mahdi On Mon, Feb 22, 2021 at 11:36 PM Ian

[go-nuts] How Go Build and test create file lists needed for compile, build and link when CGO is enabled

Hi, I have a problem when trying to run the test for runtime when CGO is enabled. The test I want to run is CGO_ENABLED=1 go test -run=TestCgoSignalDeadlock inside src/runtime of the goroot. This test on my machine never compile the c files and hence led to link problem while my other CGO progr

Re: [go-nuts] How CGO create _Ctype_char and other default C types? I can not build my program on machine with char being unsigned by default

020 at 12:28 PM Mahdi Hosseini > wrote: > > > > Hi, > > I try to recompile Go for a new platform which is a s390x platform using > Clang instead of GCC. I can not work for C string in CGO. Apparently char > in unsigned by default on my platform and building even the s

[go-nuts] How CGO create _Ctype_char and other default C types? I can not build my program on machine with char being unsigned by default

Hi, I try to recompile Go for a new platform which is a s390x platform using Clang instead of GCC. I can not work for C string in CGO. Apparently char in unsigned by default on my platform and building even the simple CGO program always fails with this error: */home/user/tmp/go-build468743286/b