First version of a data flow procedure language
Programming Symposium, Proceedings Colloque sur la Programmation
Anti-aliased line drawing using brush extrusion
SIGGRAPH '83 Proceedings of the 10th annual conference on Computer graphics and interactive techniques
A multiple processor data flow machine that supports generalized procedures
ISCA '81 Proceedings of the 8th annual symposium on Computer Architecture
An architecture for extended abstract data flow
ISCA '81 Proceedings of the 8th annual symposium on Computer Architecture
The semantics of graphical input
SIGGRAPH '79 Proceedings of the 6th annual conference on Computer graphics and interactive techniques
3-D transformations of images in scanline order
SIGGRAPH '80 Proceedings of the 7th annual conference on Computer graphics and interactive techniques
Data-driven implementation of data flow diagrams
ICSE '82 Proceedings of the 6th international conference on Software engineering
Chap - a SIMD graphics processor
SIGGRAPH '84 Proceedings of the 11th annual conference on Computer graphics and interactive techniques
SIGGRAPH '84 Proceedings of the 11th annual conference on Computer graphics and interactive techniques
Input-Output Tools: A Language Facility for Interactive and Real-Time Systems
IEEE Transactions on Software Engineering
A computer architecture for highly parallel signal processing
ACM '74 Proceedings of the 1974 annual ACM conference - Volume 2
Hi-index | 0.00 |
We have built a system, Patchwork, that allows programs to be organized according to a dataflow model. In our implementation, application programs use Patchwork to assemble complex microcode programs for a graphics processor from a library of microcode modules. We describe a simple and efficient implementation, in which the only overhead incurred is a single extra level of indirection when invoking a module or when a module accesses inputs, outputs, or local storage. The implementation depends on being able to describe a distinct execution tree for the network, which obviates the need both for run-time monitoring of the execution and for movement of data. Thus, neither dataflow hardware nor a dataflow language is needed for the implementation. Patchwork supports flow-of-control constructs such as looping and branching, the assembly of complex modules from simpler ones, modules written in a variety of languages for a variety of different devices, the interleaved execution of several programs on a single processor, and the execution of a single program on a set of processors in parallel. An analysis showed that Patchwork contributed between 2 and 5% to the total running time of sample microcode programs.