go/test/fixedbugs/bug108.go

// errchk $G $D/$F.go

// Copyright 2009 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

package main
func f() {
	v := 1 << 1025;		// ERROR "overflow|stupid shift"
	_ = v
}
Storing an out of range constant into a variable should ideally cause the compiler to give an error. Right now 6g warns about large shifts but does not give an error. This CL removes the out of range shift from shift.go, so that it will work with gccgo, and adds a test case in bugs/ to be fixed at a later date. R=ken,r DELTA=23 (9 added, 14 deleted, 0 changed) OCL=16085 CL=16088 2008-09-29 12:03:21 -06:00			`// errchk $G $D/$F.go`

			`// Copyright 2009 The Go Authors. All rights reserved.`
			`// Use of this source code is governed by a BSD-style`
			`// license that can be found in the LICENSE file.`

			`package main`
			`func f() {`
warn -> yyerror in mparith. close two more bugs. R=ken OCL=26226 CL=26226 2009-03-12 20:57:30 -06:00			`v := 1 << 1025; // ERROR "overflow\|stupid shift"`
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 12:50:45 -07:00			`_ = v`
Storing an out of range constant into a variable should ideally cause the compiler to give an error. Right now 6g warns about large shifts but does not give an error. This CL removes the out of range shift from shift.go, so that it will work with gccgo, and adds a test case in bugs/ to be fixed at a later date. R=ken,r DELTA=23 (9 added, 14 deleted, 0 changed) OCL=16085 CL=16088 2008-09-29 12:03:21 -06:00			`}`