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,c3a99922e4848e56
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Info on task constructs/Posix thread equivalence?
Date: 1996/06/09
Message-ID: <dewar.834362928@schonberg>#1/1
X-Deja-AN: 159353423
references: <4peeng$8be@goanna.cs.rmit.EDU.AU>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-06-09T00:00:00+00:00
List-Id: <comp.lang.ada>


Dale said

"I've never come across any documents that described how Gnat
handles the mapping (and not being compiler conversant, I'm
hesitant to delve into the compiler)."

There is a printed document, but it is out of date, the current 
documenttion is in the sources (where it has a much better chance
of staying up to date).

You don't need to be compiler conversant here, we are talking about
runtime routines, which are just Ada code! Start by looking at the
s-taspri.ads and s-taspri.adb units which are the low level mapping
from GNULL (the low level interface) to Pthreads.

Note that even the binary distributions have full copies of the run time
sources, just so this is easy to do!

If you want to look at the high level interface, the easiest thing is to
run the compiler on various tasking constructs with -gnatdg, that will
show you the low level code, including the calls to the tasking runtime.