here - Stefan-Marr.de

More documents

Recommendations

Info

3. Which Concepts for Concurrent and Parallel Progr. does a VM need to Support? survey is the set of VMs that are used as runtime platforms for a wide range of languages for a single system. Thus, distributed VMs such as the PVM [Geist et al., 1994] are not considered because they solve a distinct set of problems such as physical distribution and fault tolerance, which are outside of the scope of this dissertation. This survey considers the Java Virtual Machine (JVM) [Lindholm et al., 2012], the Common Language Infrastructure (CLI) [ECMA International, 2010], and the Parrot VM to be multi-language VMs. The JVM is with the addition of the invokedynamic bytecode [Rose, 2009; Thalinger and Rose, 2010] explicitly designed to host a wider range of languages. The CLI and Parrot VM 1 have been explicitly designed as execution platforms for multiple languages from the beginning. Because of its close relation to the JVM (cf. Sec. 3.1.2.1), the survey includes the Dalvik VM as a multi-language VM, as well. While JavaScript and its VMs have not been designed as multi-language platforms, wide availability led to their adoption as a platform for language implementation. 2 Therefore, this survey includes JavaScript as well. The discussion is based on JavaScript’s standardized form ECMAScript [ECMA International, 2011] and the upcoming HTML5 standard to cover WebWorkers 3 as a mechanism for concurrent programming. To complement these multi-language VMs, this survey includes additional VMs that either support relevant concurrent and parallel programming concepts, or have contributed to VM implementation techniques. The selected VMs are: DisVM [Lucent Technologies Inc and Vita Nuova Limited, 2003], Erlang [Armstrong, 2007], Glasgow Haskell Compiler (GHC), Mozart/Oz, Perl, 4 Python, 5 Ruby, 6 Self [Chambers et al., 1989], and Squeak [Ingalls et al., 1997]. An overview over the subjects, including the relevant version information is given in Tab. 3.1. 3.1.1.3. Survey Execution For each subject of the survey, the analysis uses the VM specification if it is available and if it provides sufficient information for the assessment. Otherwise, it examines the source code of the implementation and the language 1 Parrot – speaks your language, Parrot Foundation, access date: 4 December 2012 http://www.parrot.org/ 2 altJS, David Griffiths, access date: 4 December 2012 http://altjs.org/ 3 http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html 4 http://perldoc.perl.org/perl.html 5 http://docs.python.org/release/3.2.3/ 6 http://www.ruby-lang.org/en/documentation/ 42
3.1. VM Support for Concurrent and Parallel Programming VM Spec. Src. Version CLI X 5th edition Dalvik X Android 4.0 DisVM X 4th edition ECMAScript+HTML5 X X ECMAScript5.1, HTML5 Erlang X Erlang/OTP R15B01 GHC X GHC 7.5.20120411 JVM X X Java SE 7 Edition Mozart X 1.4.0.20080704 Perl X 5.14.2 Python X 3.2.3 Ruby X 1.9.3 Self X 4.4 Squeak X X 4.3 Table 3.1.: VM survey subjects, their version, and the availability of specification and source code. documentation. For example, the CLI’s specification describes the relevant parts of the standard library and is therefore deemed to be sufficient. For the JVM however, the analysis includes one of the actual implementations (HotSpot and OpenJDK 7 ) and its accompanying documentation since the standard library is not covered by the specification. In the case of ECMAScript and HTML5, the specification is complemented with an analysis of the implementations based on V8 8 and SpiderMonkey 9 For languages without specification such as PHP, Python, or Ruby, the analysis includes only the implementation that is widely regarded to be the official, i. e., standard implementation, as well as the available documentation. To answer the survey questions, the analysis assesses whether a concept is realized with the help of VM support or purely as a library. For VMs where only the specification was examined, the assessment was deduced from this information. For VMs where the implementation was inspected, the decision was simpler. A concept is considered to be realized as a library if its implementation is written completely in the language provided by the VM. None of the VM’s primitives, i. e., mechanisms directly provided by the VM are an essential part of the concept’s implementation. This criterion was unambiguous in this survey because none of the inspected implementations relied on a 7 http://openjdk.java.net/ 8 https://github.com/v8/v8/archive/3.9.24.zip 9 http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/12.0b5/ 43
Page 1 and 2:
Faculty of Science and Bio-Engineer
Page 3:
DON’T PANIC
Page 7:
S A M E N VAT T I N G Over de laats
Page 11 and 12:
C O N T E N T S 1. Introduction 1 1
Page 13 and 14: Contents 4.4. RoarVM . . . . . . .
Page 15: Contents 9.5. Future Work . . . . .
Page 19: L I S T O F TA B L E S 2.1. Flynn
Page 22 and 23: List of Listings 7.2. Applying tran
Page 24 and 25: 1. Introduction of solutions for di
Page 26 and 27: 1. Introduction traded in for bette
Page 28 and 29: 1. Introduction ad hoc implementati
Page 30 and 31: 1. Introduction Chapter 7: Implemen
Page 32 and 33: 1. Introduction and systems [De Kos
Page 34 and 35: 1. Introduction ReBench This disser
Page 36 and 37: 2. Context and Motivation 2.1. Mult
Page 38 and 39: 2. Context and Motivation in litera
Page 40 and 41: 2. Context and Motivation e. g., ar
Page 42 and 43: 2. Context and Motivation tasks wit
Page 44 and 45: 2. Context and Motivation section.
Page 46 and 47: 2. Context and Motivation Table 2.1
Page 48 and 49: 2. Context and Motivation The remai
Page 50 and 51: 2. Context and Motivation Clojure A
Page 52 and 53: 2. Context and Motivation To achiev
Page 54 and 55: 2. Context and Motivation Each vat
Page 56 and 57: 2. Context and Motivation driven to
Page 58 and 59: 2. Context and Motivation 2.5. Buil
Page 60 and 61: 2. Context and Motivation First, it
Page 62 and 63: 3. Which Concepts for Concurrent an
Page 111 and 112: 4 E X P E R I M E N TAT I O N P L A
Page 113 and 114: 4.2. SOM: Simple Object Machine SOM
Page 115 and 116:
4.2. SOM: Simple Object Machine 1 S
Page 117 and 118:
4.2. SOM: Simple Object Machine nee
Page 119 and 120:
4.2. SOM: Simple Object Machine 1 S
Page 121 and 122:
4.2. SOM: Simple Object Machine HAL
Page 123 and 124:
4.4. RoarVM Used Software and Libra
Page 125 and 126:
4.4. RoarVM that is performance cri
Page 127 and 128:
4.4. RoarVM Table 4.2.: The Smallta
Page 129 and 130:
4.4. RoarVM is a problematic operat
Page 131 and 132:
5 A N O W N E R S H I P - B A S E D
Page 133 and 134:
5.1. Open Implementations and Metao
Page 135 and 136:
5.2. Design of the OMOP metaclass-b
Page 137 and 138:
5.2. Design of the OMOP Meta Level
Page 139 and 140:
5.2. Design of the OMOP set of mech
Page 141 and 142:
5.3. The OMOP By Example current :
Page 143 and 144:
5.3. The OMOP By Example dling writ
Page 145 and 146:
5.3. The OMOP By Example The proces
Page 147 and 148:
5.4. Semantics of the MOP 1 SOMObje
Page 149 and 150:
5.4. Semantics of the MOP 1 SOMInte
Page 151 and 152:
5.5. Customizations and VM-specific
Page 153 and 154:
5.6. Related Work how to use it to
Page 155 and 156:
5.6. Related Work In ABCL/R2, meta-
Page 157:
5.7. Summary which owns a set of ob
Page 160 and 161:
6. Evaluation: The OMOP as a Unifyi
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 203 and 204:
7 I M P L E M E N TAT I O N A P P R
Page 205 and 206:
7.1. AST Transformation VMs makes s
Page 207 and 208:
7.1. AST Transformation all have th
Page 209 and 210:
7.1. AST Transformation because thi
Page 211 and 212:
7.2. Virtual Machine Support ments
Page 213 and 214:
7.2. Virtual Machine Support to the
Page 215 and 216:
7.2. Virtual Machine Support 1 void
Page 217 and 218:
7.2. Virtual Machine Support 1 void
Page 219 and 220:
7.2. Virtual Machine Support Table
Page 221:
7.3. Summary the RoarVM, primitives
Page 224 and 225:
8. Evaluation: Performance 8.1. Eva
Page 226 and 227:
8. Evaluation: Performance tional c
Page 228 and 229:
8. Evaluation: Performance The goal
Page 230 and 231:
8. Evaluation: Performance benchmar
Page 232 and 233:
8. Evaluation: Performance General
Page 234 and 235:
8. Evaluation: Performance Runtime
Page 236 and 237:
8. Evaluation: Performance 1.10 1.0
Page 238 and 239:
8. Evaluation: Performance all OMOP
Page 240 and 241:
8. Evaluation: Performance 31.62 Am
Page 242 and 243:
8. Evaluation: Performance Runtime,
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
8. Evaluation: Performance hide inh
Page 254 and 255:
8. Evaluation: Performance Conclusi
Page 256 and 257:
8. Evaluation: Performance improve
Page 258 and 259:
9. Conclusion and Future Work 9.1.
Page 260 and 261:
9. Conclusion and Future Work • C
Page 262 and 263:
9. Conclusion and Future Work A sol
Page 264 and 265:
9. Conclusion and Future Work The p
Page 266 and 267:
9. Conclusion and Future Work the a
Page 268 and 269:
9. Conclusion and Future Work all r
Page 271 and 272:
A A P P E N D I X : S U RV E Y M AT
Page 273 and 274:
A.1. VM Support for Concurrent and
Page 275 and 276:
A.1. VM Support for Concurrent and
Page 277 and 278:
A.2. Concurrent and Parallel Progra
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
B A P P E N D I X : P E R F O R M A
Page 285 and 286:
B.1. Benchmark Characterizations LR
Page 287 and 288:
B.1. Benchmark Characterizations We
Page 289 and 290:
B.2. Benchmark Configurations B.2.
Page 291:
B.2. Benchmark Configurations 101 p
Page 294 and 295:
References Joe Armstrong. A history
Page 296 and 297:
References Zoran Budimlic, Aparna C
Page 298 and 299:
References Koen De Bosschere. Proce
Page 300 and 301:
References Yaoqing Gao and Chung Kw
Page 302 and 303:
References Michael Haupt, Stefan Ma
Page 304 and 305:
References ISO. ISO/IEC 14882:2011
Page 306 and 307:
References Tim Lindholm, Frank Yell
Page 308 and 309:
References on Modularity In Systems
Page 310 and 311:
References Johan Östlund, Tobias W
Page 312 and 313:
References Tardieu. The asynchronou
Page 314 and 315:
References Matthew J. Sottile, Timo
Page 316 and 317:
References ming in mobile ad hoc ne
Page 318:
References 3-14, New York, NY, USA,
show all

here - Stefan-Marr.de

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?