You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regenerating builtin.go is tricky currently because it needs a working compiler that can generate export data in the same format as the new compiler can handle. We should replace it with something simpler.
I propose instead of generating export data for builtin/runtime.go, we just generate code/tables to directly construct the stub information. This can be done using just go/ast.
The text was updated successfully, but these errors were encountered:
Reuse the same mechanisms for handling universal builtins like len to
handle unsafe.Sizeof, etc. Allows us to drop package unsafe's export
data, and simplifies some code.
Updates #17508.
Change-Id: I620e0617c24e57e8a2d7cccd0e2de34608779656
Reviewed-on: https://go-review.googlesource.com/31433
Run-TryBot: Matthew Dempsky <mdempsky@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Robert Griesemer <gri@golang.org>
Regenerating builtin.go is tricky currently because it needs a working compiler that can generate export data in the same format as the new compiler can handle. We should replace it with something simpler.
I propose instead of generating export data for builtin/runtime.go, we just generate code/tables to directly construct the stub information. This can be done using just go/ast.
The text was updated successfully, but these errors were encountered: