In addition to the tests you saw, there are a bunch of tests in test/codegen that makes sure specific sequences of instructions are or are not generated. Tests for specific issues that have been fixed are in test/fixedbugs. Generally the whole test suite is one giant compiler test. Run all.bash and if it passes, you can be pretty sure the compiler is generating correct code. There are other tests, like compilebench, which you can use to check the resource use of the compiler.
On Thursday, September 19, 2019 at 3:28:04 PM UTC-7, Mohit Verma wrote: > > Hi, > > I added a new pass to Go SSA for experimental purposes. Is there a > testsuite to make sure Go's SSA backend works as intended? I do see some > test files in ssa/ and gc/ directory but they seem to be testing specific > cases in the code. > For example, Are there > 1. tests that would test the compilation of big files? > OR, 2. tests to make sure high-level code constructs (like FOR LOOP) > compile down to no more than "x" instructions for some value of x? > > Or is there a general testsuite that language developers use to test > compiler changes? I see this: > https://github.com/Byron/benchmarksgame-cvs-mirror but I am not sure if > this is the right place to look at. > > > Thanks! > Mohit > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/cc238d35-fc59-4572-bd2c-df5dda7539b0%40googlegroups.com.
