From: Olivier Zendra <Olivier.Zendra@inria.fr>
To: Olivier ZENDRA <Olivier.Zendra@inria.fr>
Subject: [Caml-list] ICOOOLPS 2014 Call For Participation
Date: Mon, 30 Jun 2014 14:20:32 +0200 [thread overview]
Message-ID: <943CE784-F44D-4033-ADB2-6720A8FEE0F0@inria.fr> (raw)
Call For Participation for ICOOOLPS 2014
(9th Workshop on Implementation, Compilation, Optimization of
Object-Oriented Languages, Programs and Systems),
http://icooolps.loria.fr/
28th July 2014, Uppsala, Sweden.
Co-located with ECOOP.
In cooperation with ACM SIGPLAN and ACM SIGSOFT.
Program
*******
09:00-10:00
Invited talk: Handcrafting VMs for dynamic languages: reality and dreams
Vyacheslav Egorov, Google
10:00-10:30 Break
10:30-12:00
An Efficient Approach for Accessing C Data Structures from JavaScript
Matthias Grimmer, Thomas Würthinger, Andreas Wöß, Hanspeter Mössenböck
Data Interface + Algorithms = Efficient Programs
Mattias De Wael, Stefan Marr, Wolfgang De Meuter
We are all Economists Now: Economic Utility for Multiple Heap Sizing
Callum Cameron, Jeremy Singer
12:00-13:30 Lunch
13:30-15:00
A Way Forward in Parallelising Dynamic Languages
Remigius Meier, Armin Rigo
Clash of the Lambdas
Aggelos Biboudis, Nick Palladinos, Yannis Smaragdakis
Discussion period
15:00-15:30 Break
15:30-17:00
The GOOL system: An lightweight Object-Oriented Programming language translator
Pablo Arrighi, Johan Girard, Miguel Lezama, Kévin Mazet
Why Inheritance Anomaly Is Not Worth Solving
Vincent Gramoli, Andrew E. Santosa
Discussion period
Overview
*********
The ICOOOLPS workshop series brings together researchers and practitioners
working in the field of OO languages implementation and optimization.
ICOOOLPS key goal is to identify current and emerging issues relating to
the efficient implementation, compilation and optimization of such languages,
and outlining future challenges and research directions.
Topics of interest for ICOOOLPS include, but are not limited to: implementation
of fundamental OO and OO-like features (e.g. inheritance, parametric types,
memory management, objects, prototypes), runtime systems (e.g. compilers,
linkers, virtual machines, garbage collectors), optimizations (e.g. static or
dynamic analyses, adaptive virtual machines), resource constraints (e.g. time
for real-time systems, space or low-power for embedded systems) and relevant
choices and tradeoffs (e.g. constant time vs. non-constant time mechanisms,
separate compilation vs. global compilation, dynamic loading vs. global
linking, dynamic checking vs. proof-carrying code...).
Organisation
************
Chairs:
Laurence Tratt, King's College London, UK
Olivier Zendra, INRIA Nancy, FR
Email: icooolps14@easychair.org
Programme committee
*******************
Carl Friedrich Bolz, King's College London, UK
Eric Jul, University of Copenhagen, DK
José Manuel Redondo López, Universidad de Oviedo, ES
Stefan Marr, INRIA Lille, FR
Floréal Morandat, Labri, FR
Todd Mytkowicz, Microsoft, US
Tobias Pape, Hasso-Plattner-Institut Potsdam, DE
Ian Rogers, Google, US
Jeremy Singer, University of Glasgow, UK
Jan Vitek, Purdue University, US
Mario Wolczko, Oracle Labs, US
---
Olivier ZENDRA,
Ph.D., INRIA Researcher
Olivier.Zendra@inria.fr
+33 354 958 407
http://www.loria.fr/~zendra
INRIA Nancy - Grand Est / LORIA,
Office C-124,
615 Rue du Jardin Botanique,
CS 20101
54603 VILLERS-LES-NANCY Cedex,
FRANCE
reply other threads:[~2014-06-30 12:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=943CE784-F44D-4033-ADB2-6720A8FEE0F0@inria.fr \
--to=olivier.zendra@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox