Why New Stacks Are Essential for Enhancing Parallelism and Programming Productivity

DESCRIPTION

This session explores the challenges posed by existing software stacks that limit the ability to fully utilize modern parallel computing. It emphasizes the need for innovative stacks that promote cross-layer improvements to overcome obstacles, enhance programming ease, and boost performance. Key themes include the role of diverse programming approaches, the balance between performance and productivity, security considerations, and the importance of coherent leadership. Attendees will learn how to assess and measure progress in resolving these challenges and advancing greater freedom across computational layers.

Download

1 / 1

May 11, 2026

Download Presentation

1 parallel computing 2 software stacks 3 programming productivity 4 crosslayer improvement 5 security guarantees 6 coherent leadership 7 performance metrics 8 automatic tuning text

Télécharger la présentation

Why New Stacks Are Essential for Enhancing Parallelism and Programming Productivity

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

Stacks breakout session • Why new stacks as a research proposition? • Existing stack imposes obstacles to parallelism. “Only heroic programmers can exploit the vast parallelism in today’s machines” - suggests need for cross layer improvement • Diversity • Performance vs ease of programming (productivity) • Explore alternatives • Security guarantees • Coherent guidance: generalist leadership • How to do it? Proposer should be as specific as possible: • How bad are the obstacles and how well can they improve • The ability to reason analytically • How to measure progress across levels. • Advancing degrees of freedoms across layers that will allow better automatic tuning • Non-vendor have greater flexibility, since not tied by strict backwards compatibility