An assessment of Multilisp: Lessons from experience (Q1091113)
From MaRDI portal
| This is the item page for this Wikibase entity, intended for internal use and editing purposes. Please use this page instead for the normal view: An assessment of Multilisp: Lessons from experience |
scientific article; zbMATH DE number 4009794
| Language | Label | Description | Also known as |
|---|---|---|---|
| English | An assessment of Multilisp: Lessons from experience |
scientific article; zbMATH DE number 4009794 |
Statements
An assessment of Multilisp: Lessons from experience (English)
0 references
1986
0 references
Multilisp is a parallel programming language derived from the scheme dialect of Lisp by addition of the future construct. It has been implemented on Concert, a 32-processor shared-memory multiprocessor. A statistics-gathering feature of Concert Multilisp produces parallelism profiles showing the number of processors busy with computing or overhead, as a function of time. Experience gained using parallelism profiles and other measurement tools on several application programs has revealed three basic ways in which future generates concurrency. These ways are illustrated on two example programs: the Lisp mapping function mapcar and the partitioning routine from Quicksort. Experience with Multilisp programming exposes issues relating to side effects, error and exception handling, low-level operations for explicit manipulation of futures and tasks, and speculative computing, which are also discussed. The basic outlines of Multilisp are now fairly clear and have stood the test of being used for several applications, but further language design work is especially needed in the areas of speculative computing and exception handling.
0 references
parallel symbolic computing
0 references
performance evaluation
0 references
parallel programming language
0 references
Lisp
0 references
future construct
0 references
multiprocessor
0 references
parallelism profiles
0 references
concurrency
0 references
Quicksort
0 references
error and exception handling
0 references