Call for Abstract for CnC-2014: The Sixth Annual Concurrent Collections Workshop

Call for Abstract for CnC-2014: The Sixth Annual Concurrent Collections Workshop

____________________________________________________________________________________

Call for Abstracts:

 

 CnC-2014: The Sixth Annual Concurrent Collections Workshop

http://cass-mt.pnnl.gov/cnc2014

 

September 18-19, 2014 at Intel Corporation, Hillsboro, OR (co-located with LCPC'14)

____________________________________________________________________________________

 

Important Dates

Abstracts Due: August 8, 2014

Notification: August 22, 2014

Programming Contest Notice of Participation Due: August 8, 2014

Programming Contest Written Submissions Due: September 12, 2014

Workshop: September 18-19, 2014

 

About

The annual Concurrent Collections (CnC) workshop is a forum for researchers and

developers of parallel programs to interact on a variety of issues related to next-generation

parallel programming models. The focus is on fostering a community around the CnC

programming model; however, we also strongly encourage participation by anyone with an

interest in programming models inspired by dataflow and/or tuple space ideas as well as

current or emerging applications of such models.

 

Participation and Call for Abstracts

The workshop agenda will include CnC tutorials on current and future trends, talks selected

from contributed abstracts, and a programming contest. Topics of interest include, but are not

limited to: language design and implementation, semantics and theory, application experiences,

and teaching of CnC.

 

If you would like to give a talk, please submit a short abstract (between 200 and 500 words

in length) by August. 8, 2014 to both workshop chairs at sanjay.chatterjee@intel.com and

john.feo@pnnl.gov.

 

Programming Contest

This year for the first time, we are challenging small teams (as small as 1) of CnC developers to

compete in a programming contest. If you are interested in competing please send a team name,

list of team members, and a problem of choice by August 8, 2014 to both workshop chairs. We

encourage you to work with the workshop committee to define an appropriate problem. Solutions

will be judged on creativity, programming style, solution, and performance. A written report,

including source code, is due by September 12, 2014 to both workshop chairs. We will reserve a

session on the first day of the workshop for teams to present their work. While presenting is not

required, it is highly encouraged as it provides an opportunity for the committee and audience to

better understand your work. A significant prize will be awarded to the winning team at the close

of the workshop.

 

Background on CnC

CnC is a parallel programming model for mainstream programmers that differs from other

approaches in its philosophy. A CnC programmer doesn't specify parallel operations; instead,

he/she only specifies semantic ordering constraints. This provides a separation of concerns

between the domain expert and the tuning expert, simplifying the job of the domain expert

while providing more flexibility to the tuning expert. Details on CnC and related research can

be found at: http://intel.ly/concurrent-collections and http://habanero.rice.edu/cnc.

 

Prior workshops have served as a forum for users and potential users of CnC to discuss

experiences with CnC and a range of topics, including developments for the language,

applications, usability, performance, semantics, and teaching of CnC.

 

Need more information?

 

If you have any questions about logistics or participation, please contact the workshop chairs

at sanjay.chatterjee@intel.com and john.feo@pnnl.gov.
____________________________________________________________________________________

 

Chairs

Sanjay Chatterjee, Intel Corporation

John Feo, Pacific Northwest National Laboratory

 

Organizing Committee

Zoran Budimlic, Rice University

Kath Knobe, Intel

Louis-Noel Pouchet, University of California, Los Angeles

Frank Schlimbach, Intel

1 post / 0 new
For more complete information about compiler optimizations, see our Optimization Notice.