cmd/compile: PGO matching doesn't escape package paths #59887
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
Package paths that have a dot in the last component get escaped in the symbol table (and thus in profiles). e.g., in package
example.com
,main
becomesexample%2ecom.main
.When matching function names in the profile to functions in the source, we do a naive combination of package path and name (via
ir.PkgFuncName
), meaning we will fail to match these.Dots in the last component of package paths are fairly rare. Most common is probably in
gopkg.in/something.v1
.cc @cherrymui
The text was updated successfully, but these errors were encountered: