You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2ee6604408
The asm tool runs twice for a package with assembly. The second time it does, the path given to the -p flag matters, just like in the compiler, as we generate an object file. We don't have a -buildid flag in the asm tool, so obtaining the action ID to obfuscate the package path with is a bit tricky. We store it from transformCompile, and read it from transformAsm. See the detailed docs for more. This was the last "skip" line in the tests due to Go 1.16. After all PRs are merged, one last PR documenting that 1.16 is supported will be sent, closing the issue for good. It's unclear why this wasn't an issue in Go 1.15. My best guess is that the ABI changes only happened in Go 1.16, and this causes exported asm funcs to start showing up in object files with their package paths. Updates #124. |
4 years ago | |
|---|---|---|
| .. | ||
| bench | 5 years ago | |
| mod | 4 years ago | |
| scripts | 4 years ago | |