1989
DOI: 10.1109/32.21761
|View full text |Cite
|
Sign up to set email alerts
|

Experience with multiple processor versions of Concurrent C

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
4
0
2

Year Published

1990
1990
2011
2011

Publication Types

Select...
5
2
2

Relationship

1
8

Authors

Journals

citations
Cited by 16 publications
(6 citation statements)
references
References 4 publications
0
4
0
2
Order By: Relevance
“…With Concurrent C/C++ having been ported to a SM multiprocessor [17], we decided that it was necessary to provide explicit facilities for controlling access to shared memory. We felt that using the approaches mentioned above was not appropriate for "heavy duty" use.…”
Section: Motivationmentioning
confidence: 99%
“…With Concurrent C/C++ having been ported to a SM multiprocessor [17], we decided that it was necessary to provide explicit facilities for controlling access to shared memory. We felt that using the approaches mentioned above was not appropriate for "heavy duty" use.…”
Section: Motivationmentioning
confidence: 99%
“…t We are grateful to Bjarne Stroustrup for giving us the source for the C + + preprocessor. 3. In Concurrent C + + implementations that support shared memory, reference types can be used for transaction and process argument types, and as transaction return-value types.…”
Section: Class Variables Can Be Used In Process Bodies T H E Construmentioning
confidence: 99%
“…Several commercial and experimental languages for parallel programming and object-oriented programming are well developed and widely used. Some of those languages are Smalltalk [23], C++ [50][51][52][53][54][55][56] and Eiffel [41] in the object-oriented language side, and Concurrent C++ [17,21,22], Multilisp [25] and Concurrent C [58] on the parallel programming side. Also, there are several languages developed to support distributed programming.…”
Section: Introductionmentioning
confidence: 99%