Difference between revisions of "Event:DAMP 2007"

From ConfIDent
m (Text replacement - "[ \s]User:Curator 83" to " Ch")
 
(5 intermediate revisions by one other user not shown)
Line 2: Line 2:
 
|Acronym=DAMP 2007
 
|Acronym=DAMP 2007
 
|Title=Workshop on Declarative Aspects of Multicore Programming 2007
 
|Title=Workshop on Declarative Aspects of Multicore Programming 2007
 +
|Ordinal=2
 +
|In Event Series=Event Series:B56c1216-9413-48bf-92cd-5a2acddeed46
 +
|Single Day Event=yes
 +
|Start Date=2007/01/16
 +
|Event Status=as scheduled
 +
|Event Mode=on site
 +
|City=Nice
 +
|Country=Country:FR
 +
|Academic Field=Programming Paradigms
 +
|Official Website=http://www.cs.cmu.edu/~damp/
 
|Type=Workshop
 
|Type=Workshop
|Field=Programming paradigms
 
|Homepage=www.cs.cmu.edu/~damp/
 
|City=Nice
 
|Country=France
 
|Submission deadline=2006/11/03
 
 
|pageCreator=Floebe
 
|pageCreator=Floebe
 
|pageEditor=Floebe
 
|pageEditor=Floebe
 
|contributionType=1
 
|contributionType=1
|In Event Series=Event Series:DAMP
 
|Single Day Event=no
 
|Start Date=2007/01/16
 
|End Date=2007/01/16
 
 
}}
 
}}
 +
{{Event Deadline
 +
|Submission Deadline=2006/11/03
 +
}}
 +
{{Organizer
 +
|Contributor Type=organization
 +
|Organization=Special Interest Group on Programming Languages, Association for Computing Machinery
 +
}}
 +
{{Organizer
 +
|Contributor Type=organization
 +
|Organization=Special Interest Group on Algorithms and Computation Theory, Association for Computing Machinery
 +
}}
 +
{{Event Metric}}
 +
{{S Event}}
 
''Source:'' http://www.cs.cmu.edu/~damp/
 
''Source:'' http://www.cs.cmu.edu/~damp/
  
Line 50: Line 64:
 
** [[has PC member::some person]], some affiliation, country
 
** [[has PC member::some person]], some affiliation, country
 
!-- template ends -->
 
!-- template ends -->
== Description ==
+
==Description==
  
 
Parallelism is going mainstream. Many chip manufactures are turning to multicore processor designs rather than scalar-oriented frequency increases as a way to get performance in their desktop, enterprise, and mobile processors. This endeavor is not likely to succeed long term if mainstream applications cannot be parallelized to take advantage of tens and eventually hundreds of hardware threads. Parallelizing programs is a difficult problem. User specification of parallelism is fraught with pitfalls such as race conditions, non-determinism in thread interactions, a lack of debugging methods, and poorly understood performance consequences. Automatic parallelization of existing imperative languages will not meet the challenge due to dependencies and aliasing. Multicore architectures will differ in significant ways from their multisocket predecessors. For example, the communication to compute bandwidth ratio is likely to be higher, which will positively impact performance. More generally, multicore architectures introduce several new dimensions of variability in both performance guarantees and architectural contracts, such as the memory model, that may not stabilize for several generations of product.
 
Parallelism is going mainstream. Many chip manufactures are turning to multicore processor designs rather than scalar-oriented frequency increases as a way to get performance in their desktop, enterprise, and mobile processors. This endeavor is not likely to succeed long term if mainstream applications cannot be parallelized to take advantage of tens and eventually hundreds of hardware threads. Parallelizing programs is a difficult problem. User specification of parallelism is fraught with pitfalls such as race conditions, non-determinism in thread interactions, a lack of debugging methods, and poorly understood performance consequences. Automatic parallelization of existing imperative languages will not meet the challenge due to dependencies and aliasing. Multicore architectures will differ in significant ways from their multisocket predecessors. For example, the communication to compute bandwidth ratio is likely to be higher, which will positively impact performance. More generally, multicore architectures introduce several new dimensions of variability in both performance guarantees and architectural contracts, such as the memory model, that may not stabilize for several generations of product.
Line 59: Line 73:
  
 
Specific topics include, but are not limited to:
 
Specific topics include, but are not limited to:
* suitability of functional and logic programming languages to multicore applications;
+
*suitability of functional and logic programming languages to multicore applications;
* run-time issues such as garbage collection or thread scheduling;
+
*run-time issues such as garbage collection or thread scheduling;
* architectural features that may enhance the parallel performance of declarative languages;
+
*architectural features that may enhance the parallel performance of declarative languages;
* type systems for accurately knowing or limiting dependencies, aliasing, effects, and nonpure features;
+
*type systems for accurately knowing or limiting dependencies, aliasing, effects, and nonpure features;
* ways of specifying or hinting at parallelism
+
*ways of specifying or hinting at parallelism
* ways of specifying or hinting at data placement which abstract away from any details of the machine;
+
*ways of specifying or hinting at data placement which abstract away from any details of the machine;
* compiler techniques;
+
*compiler techniques;
* experiences of and challenges arising from making declarative programming practical;
+
*experiences of and challenges arising from making declarative programming practical;
* technology for debugging parallel programs
+
*technology for debugging parallel programs
* the design and implementation of domain-specific declarative languages for multi-core;
+
*the design and implementation of domain-specific declarative languages for multi-core;
  
 
We are looking for short papers (3-5) pages. These can be in the form of a position paper, new ideas, initial results, overview of ongoing research, or even a historical perspective. Submissions are due November 3; notification of acceptance will be sent by December 1; final copies will be due January 5.
 
We are looking for short papers (3-5) pages. These can be in the form of a position paper, new ideas, initial results, overview of ongoing research, or even a historical perspective. Submissions are due November 3; notification of acceptance will be sent by December 1; final copies will be due January 5.
Line 75: Line 89:
 
This workshop is a followup of the Declarative Programming Languages for Multicore Architectures 2006 which was held as part of POPL 2006.
 
This workshop is a followup of the Declarative Programming Languages for Multicore Architectures 2006 which was held as part of POPL 2006.
  
== Programm Chair: ==
+
==Programm Chair:==
 
<pre>
 
<pre>
 
Professor Guy Blelloch
 
Professor Guy Blelloch
Line 82: Line 96:
 
blelloch@cs.cmu.edu
 
blelloch@cs.cmu.edu
 
</pre>
 
</pre>
== Programme Committee ==
+
==Programme Committee==
 
<pre>
 
<pre>
 
Perry Cheng, IBM T. J. Watson Research Center
 
Perry Cheng, IBM T. J. Watson Research Center
Line 92: Line 106:
 
</pre>
 
</pre>
  
== General Chair ==
+
==General Chair==
 
<pre>
 
<pre>
 
Neal Glew
 
Neal Glew

Latest revision as of 12:03, 28 June 2023

Deadlines
2006-11-03
3
Nov
2006
Submission
organization
organization
Metrics
Venue

Nice, France

Loading map...

Source: http://www.cs.cmu.edu/~damp/

Description

Parallelism is going mainstream. Many chip manufactures are turning to multicore processor designs rather than scalar-oriented frequency increases as a way to get performance in their desktop, enterprise, and mobile processors. This endeavor is not likely to succeed long term if mainstream applications cannot be parallelized to take advantage of tens and eventually hundreds of hardware threads. Parallelizing programs is a difficult problem. User specification of parallelism is fraught with pitfalls such as race conditions, non-determinism in thread interactions, a lack of debugging methods, and poorly understood performance consequences. Automatic parallelization of existing imperative languages will not meet the challenge due to dependencies and aliasing. Multicore architectures will differ in significant ways from their multisocket predecessors. For example, the communication to compute bandwidth ratio is likely to be higher, which will positively impact performance. More generally, multicore architectures introduce several new dimensions of variability in both performance guarantees and architectural contracts, such as the memory model, that may not stabilize for several generations of product.

Programs written in functional or logic programming languages, or even in other languages with a controlled use of side effects, can greatly simplify parallel programming. Such declarative programming allows for a deterministic semantics even when the underlying implementation might be highly non-deterministic. In addition to simplifying programming this can simplify debugging and analyzing correctness.

DAMP is a one day workshop seeking to explore ideas in programming language design that will greatly simplify programming for multicore architectures, and more generally for tightly coupled parallel architectures. The emphasis will be on functional and logic programming, but any programming language ideas that aim to raise the level of abstraction are welcome. DAMP seeks to gather together researchers in declarative approaches to parallel programming and to foster cross fertilization across different approaches.

Specific topics include, but are not limited to:

  • suitability of functional and logic programming languages to multicore applications;
  • run-time issues such as garbage collection or thread scheduling;
  • architectural features that may enhance the parallel performance of declarative languages;
  • type systems for accurately knowing or limiting dependencies, aliasing, effects, and nonpure features;
  • ways of specifying or hinting at parallelism
  • ways of specifying or hinting at data placement which abstract away from any details of the machine;
  • compiler techniques;
  • experiences of and challenges arising from making declarative programming practical;
  • technology for debugging parallel programs
  • the design and implementation of domain-specific declarative languages for multi-core;

We are looking for short papers (3-5) pages. These can be in the form of a position paper, new ideas, initial results, overview of ongoing research, or even a historical perspective. Submissions are due November 3; notification of acceptance will be sent by December 1; final copies will be due January 5.

Please submit papers by sending them to guyb+damp@cs.cmu.edu. It is due by midnight PST. The title page should include the title, the authors (with contact information for the primary author), and the abstract. Please submit the paper in PDF. This workshop is a followup of the Declarative Programming Languages for Multicore Architectures 2006 which was held as part of POPL 2006.

Programm Chair:

Professor Guy Blelloch
Department of Computer Science
Carnegie Mellon University
blelloch@cs.cmu.edu

Programme Committee

Perry Cheng, IBM T. J. Watson Research Center
Gopal Gupta, University of Texas at Dallas
Kevin Hammond, University of St Andrews
Robert Harper, Carnegie Mellon University
Suresh Jagannathan, Purdue University Charles Leiserson, Massachuetts Institute of Technology Christian Lengauer, University of Passau
Simon Peyton Jones, Microsoft Research

General Chair

Neal Glew
Intel Corporation
Santa Clara, CA, USA
neal.glew@intel.com

Sponsored in part by the National Science Foundation ALADDIN Center, and by Intel Corp..

Cookies help us deliver our services. By using our services, you agree to our use of cookies.