-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: go1.15.5 breaks LDFLAGS=-std=c++14 #42606
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
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Comments
aykevl
added a commit
to tinygo-org/tinygo
that referenced
this issue
Nov 14, 2020
For details, see golang/go#42606
It looks like I have a workaround. |
deadprogram
pushed a commit
to tinygo-org/tinygo
that referenced
this issue
Nov 14, 2020
For details, see golang/go#42606
Yes, my apologies. Because it was a security patch that was kept quiet until the release, it was hard to do proper widescale testing. The workaround is to copy Closing as a dup of #42567. |
Oops, looks like I didn't properly search for duplicates first. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, with Go 1.15.5 released a few days ago.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I put two files in a new directory.
main.go
:main.cpp
:And then I ran this code using
What did you expect to see?
The following message should be printed:
This works in Go 1.15.4 at least. I've also tested some version of Go 1.14 in which it works.
What did you see instead?
It seems to me that
-std=c++14
is a perfectly safe flag, I've been using it for quite some time.I suspect #42562 is the cause.
The text was updated successfully, but these errors were encountered: