On 8/10/24 03:53, Jens Maurer wrote:
>
>
> On 10/08/2024 01.49, Phil Bouchard via Std-Proposals wrote:
>> Greetings,
>>
>> I developed lately some generic container classes that work pretty
>> efficiently in a concurrent application. I also added created a
>> thread-safe version of the shared_ptr, which is surprisingly not
>> standardized yet given the multi-core direction all platforms are
>> taking.
>
> There's std::atomic<std::shared_ptr>.

I keep forgetting about that specialization because it got standardized
with C++20 and I need using the C++17 ABI to program OpenCV and some
older Torch / Cuda library.

>> Meanwhile I was wondering if there is any interests to support the
>> framework of true parallel programming (hypercubes, etc.), or basic
>> OpenMP given memory is shared across multi-cores in general anyways?
>
> Memory is not always shared, depending on your system architecture.
>
> This is the framework for concurrency that just got into the
> Working Draft:
>
> https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p2300r10.html

Is the working draft considering modular memory then?

> What are you looking for that wouldn't be covered by that framework?

Well this is actually an intro to true parallel programming:
https://courses.grainger.illinois.edu/cs554/fa2015/notes/01_overview_8up.pdf

And I think Nvidia needs to head that direction with their architecture.
But as soon as they do then the C++ concurrent framework will need to be
rewritten again because it doesn't look like the working draft is
considering it.

>
> Jens

-- 
Fornux Logo <https://www.fornux.com/>  
*Phil Bouchard*  LinkedIn Icon
<https://www.linkedin.com/in/phil-bouchard-5723a910/> 
Founder & CEO
T: (819) 328-4743
E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com>
320-345 de la Gauchetière Ouest| Montréal (Qc), H2Z 0A2 Canada
The Best Predictable C++ Memory Manager
<https://static.fornux.com/c-superset/> Le message ci-dessus, ainsi que
les documents l'accompagnant, sont destinés uniquement aux personnes
identifiées et peuvent contenir des informations privilégiées,
confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce
message par erreur, veuillez le détruire.
This communication (and/or the attachments) is intended for named
recipients only and may contain privileged or confidential information
which is not to be disclosed. If you received this communication by
mistake please destroy all copies.