Matthew Dempsky d7cd61ceaa cmd/compile: fix inlining of constant if statements
We accidentally overlooked needing to still visit Ninit for OIF
statements with constant conditions in golang.org/cl/96778.

Fixes #24120.

Change-Id: I5b341913065ff90e1163fb872b9e8d47e2a789d2
Reviewed-on: https://go-review.googlesource.com/97475
Run-TryBot: Matthew Dempsky <mdempsky@google.com>
Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
2018-02-27 19:27:32 +00:00
..
2017-09-15 02:39:16 +00:00
2016-04-03 17:03:15 +00:00
2012-11-08 09:04:27 -08:00
2015-01-29 13:07:30 +00:00
2013-12-12 17:18:12 -08:00
2015-07-11 14:36:33 +00:00
2015-07-11 14:36:33 +00:00
2017-08-11 17:41:17 +00:00
2015-12-17 23:36:13 +00:00
2017-04-05 18:46:31 +00:00
2014-10-27 18:59:02 -04:00
2017-12-04 19:29:14 +00:00
2013-02-11 18:20:52 -05:00
2017-10-31 19:12:11 +00:00
2017-07-26 23:37:25 +00:00
2014-01-29 09:28:23 +01:00

The test directory contains tests of the Go tool chain and runtime. It includes black box tests, regression tests, and error output tests. They are run as part of all.bash.

To run just these tests, execute:

go run run.go

Standard library tests should be written as regular Go tests in the appropriate package.

The tool chain and runtime also have regular Go tests in their packages. The main reasons to add a new test to this directory are:

  • it is most naturally expressed using the test runner; or
  • it is also applicable to gccgo and other Go tool chains.