forked from Collegeville/CW20
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Novel Architectures teatime topic
- Loading branch information
Showing
2 changed files
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
20 changes: 20 additions & 0 deletions
20
WorkshopResources/TeatimeThemes/ferenbaugh-novel-architectures.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Developer Productivity on Novel Architectures (or, Surviving in the Wild West) | ||
|
||
*Teatime theme - Collegeville 2020* | ||
|
||
*Charles Ferenbaugh, Los Alamos National Laboratory* | ||
|
||
In the past decade or so, large-scale software projects have started to support | ||
novel architectures that are wildly different from the standard CPU model: | ||
multi-core, many-core, IBM Cell, GPGPU (from multiple vendors!), .... | ||
Developing for these architectures, especially when trying to write performant | ||
code, can bring particular challenges to productivity such as: | ||
|
||
- How to reconcile fast-changing new models and libraries with stable production code? | ||
- How to support new platforms without degrading performance on existing platforms? | ||
- How to deal with toolchain support (compilers, debuggers, test harnesses, ...) that is missing or immature? | ||
|
||
In this teatime we'll discuss these questions, and other related ones as they | ||
arise. Please bring your questions, experiences, failures, and successes to | ||
share with the group! | ||
|