gccgo: gcov branch coverage doesn't look quite right #3302
Description
What steps will reproduce the problem? https://groups.google.com/d/msg/golang-nuts/g8DsZaN8o9Q/hsY_83nDGiMJ What do you see instead? look at a report like http://alberts.github.com/home/alberts/deps/src/code.google.com/p/go.crypto/cast5/cast5.go.gcov.html there's lots of untaken branches in places that look like code that doesn't involve branches at all. I'm wondering if it's due to bounds checks, allocations that could fail, etc. Overall, I think these make the branch coverage numbers less useful than they could be. Which compiler are you using (5g, 6g, 8g, gccgo)? gccgo Which operating system are you using? linux Which revision are you using? (hg identify) gofrontend rev ca4aaf510222