cmd/cgo: rt0_go failure on Windows when using zig cc #43886

andrewrk · 2021-01-24T22:48:44Z

Hello, any Go developers interested in working with Zig developers on this use case?

Upstream issue: ziglang/zig#7874
Tested with go 1.15.5.

main.go

package main

//int Add(int a, int b){
//    return a+b;
//}
import "C"
import "fmt"

func main() {
	a := C.int(10)
	b := C.int(20)
	c := C.Add(a, b)
	fmt.Println(c) // 30
}

CGO_ENABLED=1 GOOS=windows GOARCH=amd64 CC="zcc" CXX="zc++" go build main.go

zcc

#!/bin/sh
zig cc -target x86_64-windows-gnu $@

zc++

#!/bin/sh
zig c++ -target x86_64-windows-gnu $@

output:

# command-line-arguments
warning: unsupported linker arg: --compress-debug-sections=zlib-gnu

It produces main.exe but when run it segfaults in runtime.rt0_go() (called from main()). Expected output is to print "30" to the console when run in cmd.exe.

Happy to chat on IRC or Discord if anyone has some ideas to try.

The text was updated successfully, but these errors were encountered:

AlexRouSg · 2021-01-24T23:37:32Z

@andrewrk does anything change if you add the -buildmode=exe flag to go build?

andrewrk · 2021-01-25T00:04:17Z

no- still get a segfault at:

0x000000014013b53c runtime.rt0_go+0x5c in main: movb	$0x1,0xfffffffffffccee7(%rip)

was go/cgo expecting the linker to do something that perhaps didn't get done here?

it looks like one of these:

go/src/runtime/asm_amd64.s

Lines 123 to 124 in d047c91

    
           MOVB	$1, runtime·isIntel(SB) 
        
           MOVB	$1, runtime·lfenceBeforeRdtsc(SB)

looks like writing to this memory is segfaulting:

go/src/runtime/runtime2.go

Lines 1095 to 1096 in d047c91

    
           isIntel              bool 
        
           lfenceBeforeRdtsc    bool

so my question would be: in what way does go emit an object for runtime2.go, and how is the address for those variables computed in the object for asm_amd64.s?

AlexRouSg · 2021-01-25T00:11:28Z

@ianlancetaylor would be the best person to talk to about this but I'm not too sure if this should be discussed here cause the issue tracker is normally for bugs and zig isn't exactly the intended/expected compiler/linker.

andrewrk · 2021-01-25T00:14:26Z

hmm I think this may be an issue with cgo though; is that in scope for this issue tracker?

dominikh · 2021-01-25T00:57:30Z

Let's keep this issue open until we know if this is a bug in zig or in Go.

mdempsky · 2021-01-25T01:29:45Z

I don't have any familiarity with using zig. Can you give instructions on how to easily reproduce this issue from a clean Linux install?

A docker image would be ideal.

Sobeston · 2021-01-25T13:29:38Z

Reproduced with go 1.15.6 linux/amd64, full output here: https://pastebin.com/BmVtawS1

@mdempsky Assuming you have go installed already, all you should need is a master copy of zig. For you this probably means getting a binary from https://ziglang.org/download/ and adding it to your path (shouldn't need any more setup than this). Personally I get my version from the "zig-git" aur package.

Sobeston · 2021-01-25T13:49:50Z

Also tested on go 1.15.7 linux/amd64; same problem https://pastebin.com/wHw49gWf.

LaPingvino · 2021-02-15T05:42:07Z

I thought maybe filtering out the zlib-gnu invocation from Go might fix it, which I did with using this for the shell wrapper:

#!/bin/bash
INVOKE=${@/-Wl,--compress-debug-sections=zlib-gnu/}
echo $INVOKE
zig cc -target x86_64-windows-gnu $INVOKE

(set invoke to $@ to see the full invocation that CGo does)

and that does seem to solve the error, but I'm not sure if the resulting binary is as expected, adding it here, cannot test because compiled on Linux ARM64: zigandgotest.zip

LaPingvino · 2021-02-15T06:39:07Z

Update: found a Windows machine to test on, running that binary doesn't give any errors but doesn't produce the desired result (fyne hello world) either.

zx2c4 · 2021-02-15T10:09:27Z

Likely fixed by https://go-review.googlesource.com/c/go/+/291630

LaPingvino · 2021-02-18T21:59:33Z

Context to @zx2c4's reference (correct me if I'm wrong...): LLVM builds seem to have been broken for Windows with CGo before, but it wasn't really an issue until trying to get ARM64 on Windows to work. Fixes are applied now to get Windows/ARM64 working, and those should fix Windows builds across the board.

zx2c4 · 2021-02-18T22:01:54Z

Those fixes haven't been applied yet. I'm hoping @rsc will submit them with the rest of the windows/arm64 series in the near future.

LaPingvino · 2021-02-18T22:03:58Z

Yeah, the patch you refer to is still stuck in trybot-hell atm xD. If you have a branch with these fixes applied I would love to test that for the purpose of this bug.

zx2c4 · 2021-02-18T22:27:17Z

Here's what I'm building with at the moment: https://download.wireguard.com/windows-toolchain/distfiles/go1.16-2021-02-18.zip It's 1.16 plus a bunch of extras. Cgo works with Clang but I haven't tried zig's wrapper yet. Let me know how it goes.

LaPingvino · 2021-02-18T22:48:32Z

$ CC="zcc" CGO_ENABLED=1 GOOS=windows GOARCH=amd64 go build
# fyne-hello
warning: unsupported linker arg: --compress-debug-sections=zlib-gnu

zigandgotest.zip

LaPingvino · 2021-02-18T22:53:29Z

Tested with wine on my amd64 system: works. Might need to file the unsupported linker arg thing separately. So it's very likely that this bug will be fixed when the Windows/ARM64 patches are in.

LaPingvino · 2021-02-19T00:18:00Z

The argument order patch should fix the zlib-gnu warning, @zx2c4 said to check out that patch and with a bit of luck I will be able to test that too.

LaPingvino · 2021-02-19T01:30:47Z

@zx2c4 as we found that your version works, maybe link/mention the relevant bugs here so Github can help us keep track if we can close this bug?

LaPingvino · 2021-03-02T13:45:20Z

The argument order patch should fix the zlib-gnu warning, @zx2c4 said to check out that patch and with a bit of luck I will be able to test that too.

Doesn't seem to be an order patch yet? Current master seems to fix issue otherwise 👍 (while still needing the workaround)

qmuntal · 2023-10-18T13:30:20Z

CL 291630 fixed this issue. Closing.

andrewrk mentioned this issue Jan 24, 2021

use case: using zig cc to cross compile a cgo program for windows ziglang/zig#7874

Closed

This comment has been minimized.

Sign in to view

mdempsky changed the title ~~use case: using zig cc to cross compile a cgo program for windows~~ cmd/cgo: rt0_go failure on Windows when using zig cc Jan 25, 2021

mdempsky added NeedsInvestigation help wanted labels Jan 25, 2021

mdempsky added this to the Unplanned milestone Jan 25, 2021

AlexRouSg mentioned this issue Mar 1, 2021

cmd/cgo, cmd/link: with zig as CC/CXX, relocation target not defined, fatal error, SIGSEGV when compiling net/http #44695

Closed

gopherbot added the compiler/runtime label Jul 13, 2022

mknyszek added this to Go Compiler / Runtime Jul 13, 2022

mknyszek removed this from Go Compiler / Runtime Jul 13, 2022

qmuntal added the OS-Windows label Sep 28, 2023

qmuntal closed this as completed Oct 18, 2023

golang locked and limited conversation to collaborators Oct 17, 2024

gopherbot added the FrozenDueToAge label Oct 17, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cmd/cgo: rt0_go failure on Windows when using zig cc #43886

cmd/cgo: rt0_go failure on Windows when using zig cc #43886

andrewrk commented Jan 24, 2021 •

edited

Loading

This comment has been minimized.

AlexRouSg commented Jan 24, 2021

andrewrk commented Jan 25, 2021 •

edited

Loading

AlexRouSg commented Jan 25, 2021

andrewrk commented Jan 25, 2021

dominikh commented Jan 25, 2021

mdempsky commented Jan 25, 2021

Sobeston commented Jan 25, 2021

Sobeston commented Jan 25, 2021

LaPingvino commented Feb 15, 2021

LaPingvino commented Feb 15, 2021

zx2c4 commented Feb 15, 2021

LaPingvino commented Feb 18, 2021

zx2c4 commented Feb 18, 2021

LaPingvino commented Feb 18, 2021

zx2c4 commented Feb 18, 2021

LaPingvino commented Feb 18, 2021

LaPingvino commented Feb 18, 2021 •

edited

Loading

LaPingvino commented Feb 19, 2021

LaPingvino commented Feb 19, 2021

LaPingvino commented Mar 2, 2021

qmuntal commented Oct 18, 2023

cmd/cgo: rt0_go failure on Windows when using zig cc #43886

cmd/cgo: rt0_go failure on Windows when using zig cc #43886

Comments

andrewrk commented Jan 24, 2021 • edited Loading

This comment has been minimized.

AlexRouSg commented Jan 24, 2021

andrewrk commented Jan 25, 2021 • edited Loading

AlexRouSg commented Jan 25, 2021

andrewrk commented Jan 25, 2021

dominikh commented Jan 25, 2021

mdempsky commented Jan 25, 2021

Sobeston commented Jan 25, 2021

Sobeston commented Jan 25, 2021

LaPingvino commented Feb 15, 2021

LaPingvino commented Feb 15, 2021

zx2c4 commented Feb 15, 2021

LaPingvino commented Feb 18, 2021

zx2c4 commented Feb 18, 2021

LaPingvino commented Feb 18, 2021

zx2c4 commented Feb 18, 2021

LaPingvino commented Feb 18, 2021

LaPingvino commented Feb 18, 2021 • edited Loading

LaPingvino commented Feb 19, 2021

LaPingvino commented Feb 19, 2021

LaPingvino commented Mar 2, 2021

qmuntal commented Oct 18, 2023

andrewrk commented Jan 24, 2021 •

edited

Loading

andrewrk commented Jan 25, 2021 •

edited

Loading

LaPingvino commented Feb 18, 2021 •

edited

Loading