cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 23:53:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

remove invalid contant and update to Go 1.16 for inline rules

Go101 2021-05-12 03:38:19 -04:00
parent 6361964499
commit 0d20d71c9d
1 changed files with 1 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
CompilerOptimizations.md

@ -27,18 +27,6 @@ For a map `m` of type `map[string]T` and `[]byte b`, `m[string(b)]` doesn't allo
* **gc:** 1.4+ * **gc:** 1.4+
* **gccgo:** ? * **gccgo:** ?
### `switch` on `[]byte`(s)
No allocation done on the `switch` line.
```go
var b []byte
switch string(b) {
case "AA":
// ...
}
```
### `range` over `[]byte`(s) ### `range` over `[]byte`(s)
No allocation when converting a `string` into a `[]byte` for ranging over the bytes: No allocation when converting a `string` into a `[]byte` for ranging over the bytes:
@ -83,7 +71,7 @@ Gc compiler does global escape analysis across function and package boundaries.
Only short and simple functions are inlined. To be inlined a function must conform to the rules: Only short and simple functions are inlined. To be inlined a function must conform to the rules:
- function should be simple enough, the number of AST nodes must less than the budget (80); - function should be simple enough, the number of AST nodes must less than the budget (80);
- function doesn't contain complex things like loops, closures, defer, recover, select, etc; - function doesn't contain complex things like closures, defer, recover, select, etc;
- function isn't prefixed by go:noinline; - function isn't prefixed by go:noinline;
- function isn't prefixed by go:uintptrescapes, since the escape information will be lost during inlining; - function isn't prefixed by go:uintptrescapes, since the escape information will be lost during inlining;
- function has body; - function has body;