3 Commits

Author	SHA1	Message	Date
Jason Travis	19040ac871	test/bench/go1: fix typo in parserdata_test.go comment ... Change-Id: Iaca02660bdc8262db2b003a94aca661b5cec5576 Reviewed-on: https://go-review.googlesource.com/38437 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>	2017-03-22 03:23:16 +00:00
Emmanuel Odeke	53fd522c0d	all: make copyright headers consistent with one space after period ... Follows suit with https://go-review.googlesource.com/#/c/20111. Generated by running $ grep -R 'Go Authors. All' * | cut -d":" -f1 | while read F;do perl -pi -e 's/Go Authors. All/Go Authors. All/g' $F;done The code in cmd/internal/unvendor wasn't changed. Fixes #15213 Change-Id: I4f235cee0a62ec435f9e8540a1ec08ae03b1a75f Reviewed-on: https://go-review.googlesource.com/21819 Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>	2016-05-02 13:43:18 +00:00
Dave Cheney	6423682019	test/bench/go1: add go/parser benchmark ... As discussed in https://groups.google.com/d/msg/golang-dev/Na9XE6mcQyY/zbeBI7R-vnoJ Here is a static copy of the go/parser benchmark. I ended up using fancy encodings because the original parser.go had a number of `s scattered throughout which made it hard to embed the source directly. Curiously on my laptop this benchmark always scores roughly 10% higher than the standalone benchmark. This may be down to the generation of the fasta data set triggering the cpu governor to raise the cpu speed. However the benchmark is consistent with itself across multiple runs. R=golang-dev, minux.ma, rsc CC=golang-dev https://golang.org/cl/6305055	2012-06-07 10:23:45 +10:00