-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gollvm: error in backend: Segmented stacks do not support vararg functions. Building goptuna, go-sqlite3 #41399
Comments
This is a known limitation of the LLVM back end and its implementation of -fsplit-stack; to the best of my knowledge this restriction dates back to the original segmented stack support added in 2011. One thing that I can't quite understand is how -fsplit-stack is winding up on the command line in the first place, however. In your "go env" output I see GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build762480405=/tmp/go-build -gno-record-gcc-switches -funwind-tables" which does not include "-fsplit-stack" -- when building C files for cgo, there is no reason to include this option. |
So you would recommend to modify my $GOGCCFLAGS and remove them, to trying again? |
I will try to call clang manually, without -fsplit-stack flag |
OK, it looks as though -fsplit-stack is being added explicitly by the Go command (I thought this was something specific to gollvm, but I see the same thing with gccgo). For the moment I don't have a good workaround, other than using GCC as your C compiler instead of clang. |
@thanm , could we open focused discussion within LLVM's mailing list? |
It seems that I was lucky today: my first pure gollvm related bug.
What version of Go are you using (
go version
)?go version go1.15rc2 gollvm LLVM 12.0.0git linux/amd64
Does this issue reproduce with the latest release?
No idea.
What operating system and processor architecture are you using (
go env
)?go env
What did you do?
What did you expect to see?
Normal building , testing pipelines - at least without datal errors.
What did you see instead?
A crash.
CC @thanm , @cherrymui
@ianlancetaylor , maybe you can commen something.
BCC @c-bata , @danderson , @cookieo9 , @larsmans , @rittneje , @gjrtimmer, @mattn
Ivan
The text was updated successfully, but these errors were encountered: