4 Commits

Author	SHA1	Message	Date
Russ Cox	0b477ef17e	test: use testlib (first 100) ... X ,s;^// \$G (\$D/)?\$F\.go *$;// compile;g X ,s;^// \$G (\$D/)?\$F\.go && \$L \$F\.\$A *$;// build;g X ,s;^// \$G (\$D/)?\$F\.go && \$L \$F\.\$A && \./\$A\.out *$;// run;g X ,s;^// errchk \$G( -e)? (\$D/)?\$F\.go *$;// errorcheck;g R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/5656082	2012-02-16 23:48:57 -05:00
Ian Lance Taylor	387e7c2742	test: explicitly use variables to avoid gccgo "not used" error ... I haven't looked at the source, but the gc compiler appears to omit "not used" errors when there is an error in the initializer. This is harder to do in gccgo, and frankly I think the "not used" error is still useful even if the initializer has a problem. This CL tweaks some tests to avoid the error, which is not the point of these tests in any case. R=golang-dev, r CC=golang-dev https://golang.org/cl/5561059	2012-01-22 11:50:45 -08:00
Ian Lance Taylor	66b261a082	Check for specific error messages in the testsuite. This ... permits testing that the compiler emits error messages for specific lines that match egrep regexps. The desired error messages are expressed using comments of the form // ERROR "regexp" R=r DELTA=90 (73 added, 8 deleted, 9 changed) OCL=15513 CL=15566	2008-09-19 14:39:49 -07:00
Rob Pike	7b409b30f2	update some tests ... SVN=124196	2008-06-23 17:13:33 -07:00