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,93db2bcd4637d4fc X-Google-Attributes: gid103376,public From: Andi Kleen Subject: Re: Runtime Error with gnat 3.10p Date: 1998/05/28 Message-ID: #1/1 X-Deja-AN: 357202840 Sender: andi@fred.muc.de References: <6kel87$ic7$1@polo.advicom.net> <356AF4B7.5EBF8617@cl.cam.ac.uk> <1998May27.203126.1@eisner> Distribution: world Organization: [posted via] Leibniz-Rechenzentrum, Muenchen (Germany) Newsgroups: comp.lang.ada Date: 1998-05-28T00:00:00+00:00 List-Id: kilgallen@eisner.decus.org (Larry Kilgallen) writes: > > > > Annex D cannot be blamed here. it is perfectly possible to implement > > full compliance with annex D without giving a proogram to seize the > > system in this manner. Annex D talks about relationship of tasks > > in your Ada program, not about their relation to other programs runningf > > on the same operating system. > > The phrase "Under Linux" would seem to have exonerated Annex D by > implying there existed one or more other operating systems where > reasonable implementation on top of POSIX.1c threads was possible. Of course it is possible to implement it under Linux without requiring privileges too, just not with the standard, unmodified LinuxThreads package. There are several userspace threads packages available (I think the GNAT runtime has its own too) that work in a single process context and don't need root for anything. Of course they all don't scale to multiple CPUs on SMP machines. -Andi