1 / 7

Are New Programming Languages Needed To Exploit Manycore Architectures?

Are New Programming Languages Needed To Exploit Manycore Architectures?. David Callahan Distinguished Engineer Parallel Computing Platform Team Visual Studio Microsoft. Why Languages Evolve :. Programming languages capture design patterns Function calls/return

darrion
Download Presentation

Are New Programming Languages Needed To Exploit Manycore Architectures?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Are New Programming Languages Needed To Exploit Manycore Architectures? David Callahan Distinguished Engineer Parallel Computing Platform Team Visual Studio Microsoft

  2. CGO-2007 Why Languages Evolve: • Programming languages capture design patterns • Function calls/return • Objects/Method Dispatch/Interfaces/Generics • Higher-order Functions inC# • Iterators (CLU versusC++ versusC#) • Access to structured data (LINQ) • Design patterns change over time • Increasing complexity with new abstraction conventions • Domain-specific uses (Snobol, MATLAB, php, Ruby) • New programmer burdens • But the new interoperates with the old… • Language constructs support application lifecycle • Architecture/development (modules, namespaces, packages) • Testing (especially defect analysis/SAL) • Performance analysis (especially “the dialog”) • Maintenance

  3. CGO-2007 Manycore Is A New Burden • A least three design patterns demand support • Services (a.k.a. Actors, CSP) – asynchronously evolving agents with private state communicating via messages • Forall – (opportunistic) nested data parallelism over partially-ordered slices of data collections • Array languages/Parallel LINQ/and sharper knives • Transactions – unordered updates to shared state • And this ignores locality…. • Chapel/X10/Fortress • Language bindings facilitate engineering automation • Load balancing • Resource management • Speculation/Deadlock-recovery

  4. CGO-2007 But, A New Language? • Yes: Isolation + Communication • Many concepts: Domains, processes, messages, channels, contracts, choice, joins, data schema, time, new failure modes • This suggests a domain-specific language for “coordination” interoperable across many existing languages • No, new features: • Forall must be tightly integrated • Fewer concepts but interwoven with data abstractions • Research: How expensive are safety nets? • Transactions should be tightly integrated to support forall • Insufficient to handle just at the coordination level

  5. We Need A Spectrum Of Solutions

  6. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related