Topic: Where next for Standard C++? Toward a parallising C++,
Author: "Alain Coetmeur" <acoetmeur@icdc.caissedesdepots.fr>
Date: 1997/11/27 Raw View
--MimeMultipartBoundary
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
why not offering in C++ primitives/directives/library
for paralelizing application, like in
High Performance Fortran...
there can be many axis:
paralelization directives like in HPF...
it is probably hard since structures are highly regular
in C++ unlike fortran... perhaps can flat array container help
like the BLAS-like of STL (like I've read from the first STL)
...
processor mapping for multi-thread... see my other message
on multi-thread extension for C++...
there just could be some library calls, pragma...
so to lock thread on processors... maybe is the problem
so open that no standardization is possible
nor valuable.
what about data parallelism, data migration, non uniform
memory access... why not put support in C++ so it could
be easy to implement data driven paralelism,
data migration, like some do on some paralelizing compilers...
Allocator and containe are good candidates for such job...
perhaps is there no need for extension...
--
Alain Coetmeur. Informatique-CDC , mailto:acoetmeur@icdc.caissedesdepots.fr
<<Mes propos n'engagent que moi. #8*). my words are only mine. >>
--MimeMultipartBoundary--
---
[ comp.std.c++ is moderated. To submit articles: try just posting with ]
[ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ]
[ FAQ: http://reality.sgi.com/employees/austern_mti/std-c++/faq.html ]
[ Policy: http://reality.sgi.com/employees/austern_mti/std-c++/policy.html ]
[ Comments? mailto:std-c++-request@ncar.ucar.edu ]