diff options
| author | Lukas Rytz <lukas.rytz@gmail.com> | 2016-01-23 21:03:10 +0100 |
|---|---|---|
| committer | Lukas Rytz <lukas.rytz@gmail.com> | 2016-01-24 13:02:04 +0100 |
| commit | 790ed59d9fe5ca396984b8a5135b7a091e4224f7 (patch) | |
| tree | d201cf146983de404728ed6e0d2f46940f44496b /test/files/jvm/patmat_opt_no_nullcheck.check | |
| parent | 8d3be4dc79cb4679fc4994c32b21e10847e5518f (diff) | |
| download | scala-790ed59d9fe5ca396984b8a5135b7a091e4224f7.tar.gz scala-790ed59d9fe5ca396984b8a5135b7a091e4224f7.tar.bz2 scala-790ed59d9fe5ca396984b8a5135b7a091e4224f7.zip | |
SI-8601 Don't treat newarray as dead code
Otherwise we lose the side effect of a `NegativeArraySizeException`.
A test for this case already exists (run/t8601b.scala), but it currently
enforces `-optimize -Ybackend:GenASM`, so it didn't trigger on the new
backend. However, PR #4814 was merged into 2.12.x and moved that test
over to the new backend and optimizer. After merging the 2.12.x into
the current optimizer branch (push-pop elimination), the test started
failing.
Also disable the optimizer for `jvm/bytecode-test-example`: it counts
the number of null checks in a method, the optimizer (rightly) eliminates
one of the two.
Diffstat (limited to 'test/files/jvm/patmat_opt_no_nullcheck.check')
0 files changed, 0 insertions, 0 deletions