From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a6b:b548:: with SMTP id e69-v6mr7834349iof.70.1529458918720; Tue, 19 Jun 2018 18:41:58 -0700 (PDT) X-Received: by 2002:a9d:5c03:: with SMTP id o3-v6mr40563otk.7.1529458918604; Tue, 19 Jun 2018 18:41:58 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!85.12.16.69.MISMATCH!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!u78-v6no639971itb.0!news-out.google.com!z3-v6ni696iti.0!nntp.google.com!d7-v6no626568itj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 19 Jun 2018 18:41:58 -0700 (PDT) In-Reply-To: <993f28de-6a64-480b-9c6e-d9714bcdef0d@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=47.185.195.62; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 47.185.195.62 References: <993f28de-6a64-480b-9c6e-d9714bcdef0d@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Ada lacks lighterweight-than-task parallelism From: "Dan'l Miller" Injection-Date: Wed, 20 Jun 2018 01:41:58 +0000 Content-Type: text/plain; charset="UTF-8" X-Received-Bytes: 2671 X-Received-Body-CRC: 1900527226 Xref: reader02.eternal-september.org comp.lang.ada:53186 Date: 2018-06-19T18:41:58-07:00 List-Id: On Tuesday, June 19, 2018 at 8:12:02 PM UTC-5, Shark8 wrote: > On Tuesday, June 19, 2018 at 4:14:17 PM UTC-6, Dan'l Miller wrote: > > > > Ada for the Cold War in 1983 would focus on tasks as the only vehicle for parallelism. Ada for the 21st century would also embrace/facilitate slices somehow, via some sort of locality of reference or via some sort of demarcation of independence. > > Don't hate on TASK! > TASK is a great construct, and particularly good for: > 1) Isolating and/or interfacing both subsystems and jobs, with the possibility of taking advantage of multiprocessor capability; > 2) Implementing protocols, via the ACCEPT construct; and > 3) at a high-level rather than the "annotated GPU assembly" we get with (eg) CUDA/C. I'm not saying anything negative about tasks. I am just saying that there should be more games to play in the casino than merely one and only one. > As for something lightweight, we're working on that in the ARG right now: > * PARALLEL DO blocks, > * Parallel LOOPs [IIRC, it might be just FOR], and > * And some other things like operators, blocking-detection, etc. Excellent! These should produce slices for numeric computations. I am not as sure that they alone(!) will necessarily produce usable slices regarding non-numeric arbitrary processing via deep call-trees of subprograms.