scala - The Scala programming language

	Commit message (Collapse)	Author	Age	Files	Lines
*	Rename -Yopt to -opt, -Yopt-warnings to -opt-warnings	Lukas Rytz	2016-05-25	1	-1/+1
\| \| \| \|	Keep -Yopt-inline-heuristics and -Yopt-trace unchanged
*	Remove GenASM, merge remaining common code snippets	Simon Ochsenreither	2015-10-27	1	-1/+1
\| \| \| \| \| \| \| \|	With GenBCode being the default and only supported backend for Java 8, we can get rid of GenASM. This commit also fixes/migrates/moves to pending/deletes tests which depended on GenASM before.
*	Warn when combining settings for the old optimizer with -YGenBCode	Lukas Rytz	2015-07-03	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Remove some unnecessary flags files - neg/t4425.flags - run/blame_eye_triple_eee-double.flags - run/blame_eye_triple_eee-float.flags Force tests that use -optimize to GenASM - neg/sealed-final-neg.flags - pos/inline-access-levels.flags - pos/inliner2.flags - pos/sealed-final.flags - pos/t3420.flags - pos/t8410.flags - run/constant-optimization.flags - run/dead-code-elimination.flags - run/elidable-opt.flags - run/finalvar.flags - run/icode-reader-dead-code.scala - run/optimizer-array-load.flags - run/synchronized.flags - run/t3509.flags - run/t3569.flags - run/t4285.flags - run/t4935.flags - run/t5789.scala - run/t6188.flags - run/t7459b-optimize.flags - run/t7582.flags - run/t7582b.flags - run/t8601.flags - run/t8601b.flags - run/t8601c.flags - run/t8601d.flags - run/t8601e.flags - run/t9003.flags Move some tests to the new optimizer - run/classfile-format-51.scala - run/classfile-format-52.scala - run/run-bug4840.flags - run/t2106.flags - run/t6102.flags
*	SI-8601 Avoid over-eager optimization of LOAD_FIELD	Jason Zaugg	2014-05-19	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	It can NPE or trigger static class initilization, we can't elimiate it without changing semantics. To make sure we don't thwart closure elimination, I've allowed DCE to eliminate a non-static LOAD_FIELD of a member of a closure class. It would be more general to track nullity of the reciever (e.g, `this` or `new Foo` cannot be null), but that would require more infrastructure in this phase. I've added a test for closure inlining based on a a suggestion by @dragos. This actually passes if we remove the (LOAD_FIELD, DROP) peephole optimization for `closelim` altogether. But I chose to adapt that optimization (only allow it for non-static, closure fields), rather then remove it alogether, in the interests of treading lightly.
*	Revert "SI-8601 Avoid over-eager optimization of LOAD_FIELD"	Adriaan Moors	2014-05-19	1	-1/+0
\| \| \| \|	This reverts commit 0b432f9cd22b6e9770852e5b331a15f0534a312c.
*	SI-8601 Avoid over-eager optimization of LOAD_FIELD	Jason Zaugg	2014-05-18	1	-0/+1
	It can NPE or trigger static class initilization, we can't elimiate it without changing semantics.