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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5f0b2f174ad085de X-Google-Attributes: gid103376,public From: mgk25@cl.cam.ac.uk (Markus Kuhn) Subject: Re: tasking in Ada and Annex D question Date: 1999/02/02 Message-ID: <796jj7$5s2$1@pegasus.csx.cam.ac.uk>#1/1 X-Deja-AN: 439699942 References: <793jl9$hf@drn.newsguy.com> Organization: U of Cambridge Computer Lab, UK Newsgroups: comp.lang.ada Date: 1999-02-02T00:00:00+00:00 List-Id: In nabbasi@earthlink.net writes: |> Since the native threads seem to give the behavior one would |> expect, wouldn't make more sense that this become the |> default when gnat is installed on Linux, and not the FSU one. The Ada for Linux team people have recently discussed this and decided to standardize on the native threads and to try and fix the kernel to achieve Annex D compliance with the native linuxthreads. Supporting both thread libraries would lead to a real maintenance hazzle, because all precompiled shared libraries provided on top of the GNAT RTS would have to be provided twice, once for linuxthreads and once for FSU. The FSU threads are primarily there to achieve formal Annex D compliance, which you can't currently do with linuxthreads, and they are otherwise of very little practical interest. They provide no concurrency when system calls block, and they provide no parallelism on multiprocessor machines, while the native linuxthreads do offer all this. Markus -- Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK Email: mkuhn at acm.org, WWW: