[golang-dev] bounds-checking elimination

I've updated the doc
<https://docs.google.com/document/d/1vdAEAjYdzjnPA9WDOQ1e4e05cYVMpqSxJYZT33Cqw2g/edit?usp=sharing>
based on the recent compiler improvements.

In particular the following examples are working as expected.

// using a hint
_ = a[3] // early bounds check
use a[1], a[2], a[3] // no bounds checks

// using decreasing constant indexes
use a[3], a[2], a[1] // one bounds check

// iterating over a slice
for i := range a {
   use a[i] // no bounds check
}


Find more examples in test/prove.go
<https://go.googlesource.com/go/+/master/test/prove.go> and in
test/loopbce.go <https://go.googlesource.com/go/+/master/test/loopbce.go>.

Again, I'm interested to know examples (especially from stdlib) where the
compiler doesn't do a good job to eliminate bounds. If you think it should
please file a bug explaining why (but make sure to check the examples
first).


joi, 17 martie 2016, 16:08:49 UTC+1, Alexandru Moșoi a scris: