ScalaOptimization - Revision history

Jaguarul: /* Author Bio */

2008-09-26T18:16:41Z

‎Author Bio

Jaguarul: /* Author Bio */

2008-09-26T17:18:13Z

‎Author Bio

Penni: /* Optimizing Higher-Order Functions in Scala */

2008-09-25T20:05:22Z

‎Optimizing Higher-Order Functions in Scala

Penni: /* Abstract */

2008-09-25T20:04:59Z

‎Abstract

Penni: /* Abstract */

2008-09-25T18:19:15Z

‎Abstract

Penni: /* Scala Optimization */

2008-09-25T16:58:00Z

‎Scala Optimization

Penni: New page: == Scala Optimization == Iulian Dragos === Abstract === http://wiki.jvmlangsummit.com/pdf/15_Dragos_scala.pdf === Author Bio === * ===...

2008-09-24T18:38:21Z

New page: == Scala Optimization == Iulian Dragos === Abstract === <update the abstract here> http://wiki.jvmlangsummit.com/pdf/15_Dragos_scala.pdf === Author Bio === * <update the bio here> ===...

New page

== Scala Optimization ==
Iulian Dragos

=== Abstract ===
<update the abstract here>

http://wiki.jvmlangsummit.com/pdf/15_Dragos_scala.pdf

=== Author Bio ===
* <update the bio here>

=== Key Issues for Discussion (cooperative) ===
''(please expand cooperatively)''
[[Talk:Scala]]

@@ Line 1: / Line 1: @@
 == Optimizing Higher-Order Functions in Scala  ==
-Julian Dragos
+Iulian Dragos
 ; Project: www.scala-lang.org

@@ Line 7: / Line 7: @@
 ; Talk Abstract: Scala relies on libraries as the default mechanism for language extension. While this provides an elegant solution for growing the language, the performance penalty incurred by call-by-name parameters, boxing and anonymous functions is high. We show that inlining alone is not enough to remove this overhead, and present a solution based on decompilation of library code combined with inlining, dead code elimination, and copy propagation. We evaluate our approach on two language extensions, Java-like assert and C-like for-loops and show improvements of up to 45%.
-http://wiki.jvmlangsummit.com/pdf/TBD
+http://wiki.jvmlangsummit.com/pdf/15_Dragos_scala.pdf
 === Author Bio ===

← Older revision		Revision as of 18:19, 25 September 2008
Line 7:		Line 7:
	; Talk Abstract: Scala relies on libraries as the default mechanism for language extension. While this provides an elegant solution for growing the language, the performance penalty incurred by call-by-name parameters, boxing and anonymous functions is high. We show that inlining alone is not enough to remove this overhead, and present a solution based on decompilation of library code combined with inlining, dead code elimination, and copy propagation. We evaluate our approach on two language extensions, Java-like assert and C-like for-loops and show improvements of up to 45%.		; Talk Abstract: Scala relies on libraries as the default mechanism for language extension. While this provides an elegant solution for growing the language, the performance penalty incurred by call-by-name parameters, boxing and anonymous functions is high. We show that inlining alone is not enough to remove this overhead, and present a solution based on decompilation of library code combined with inlining, dead code elimination, and copy propagation. We evaluate our approach on two language extensions, Java-like assert and C-like for-loops and show improvements of up to 45%.

		+	http://wiki.jvmlangsummit.com/pdf/TBD

	=== Author Bio ===		=== Author Bio ===

@@ Line 10: / Line 10: @@
 === Author Bio ===
-[http://lamp.epfl.ch/~dragos Iulian Dragos] is working on the [http://scala-lang.org Scala] compiler since 2004, being responsible of the JVM backend and compiler optimizations. He is pursuing a PhD under the supervision of [http://lamp.epfl.ch/~odersky/ Martin Odersky], at [www.epfl.ch EPFL], Switzerland. Before joining the [http://scala-lang.org Scala] group, he worked as a software engineer on a C++ car dealer management system [http://softnrg.de]. He is the author of the [http://code.google.com/p/gdata-scala-client/ Google Data Scala client], a generic library based on XML pickling combinators.
+[[Image:iuli.jpg|60px|thumb|left]]
 === Key Issues for Discussion (cooperative) ===
 ''(please expand cooperatively)''
 [[Talk:Scala]]