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 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.ada Subject: =?UTF-8?Q?Re:=20GNAT=C2=A0and=20Tasklets?= Date: Fri, 19 Dec 2014 20:45:49 +0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: <1r2ziulc78imb$.ad6zx5upic6s$.dlg@40tude.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Fri, 19 Dec 2014 20:45:49 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="0f809dda06c8e10a79188945d6c44db2"; logging-data="29545"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/6HCEsfu671gs7VhsPF2s/Buyq5D0a8v0=" User-Agent: NewsTap/4.0.1 (iPhone/iPod Touch) Cancel-Lock: sha1:at2YynkAFcXuKYOp8I22WMy7k2s= Xref: news.eternal-september.org comp.lang.ada:24161 Date: 2014-12-19T20:45:49+00:00 List-Id: "Dmitry A. Kazakov" wrote: > On Fri, 19 Dec 2014 09:42:52 -0700, Brad . In image processing when doing it by > segments, you need to sew the segments along their borders, practically in > all algorithms. That makes parallelization far more complicated to be > handled by such a blunt thing as parallel loop. Conclusions drawn from one example are fallacious here, as I am sure you know well. Take some other algorthm like Inverting all pixels, or anything written for parallel APL, or R. Anything whose parts need not be run on a full machine with I/O layers and active control. > It won't, because a big number library will use the heap or a shared part > of the stack which will require interlocking and thus will either be marked > as "impure", so that the compiler will not try to parallelize, or else will > make the compiler to use locks, which will effectively kill parallelism. All the aliasing analysis explored at SofCheck/AdaCore and considerations regarding purity and experience gained when developing the Spark language based on Ada should be a good basis for describing aspects of subprograms that are candidates for parallel execution?