From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7770 invoked by alias); 18 Oct 2002 16:17:08 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 7649 invoked from network); 18 Oct 2002 16:17:02 -0000 Received: from unknown (HELO mail.enyo.de) (212.9.189.162) by sources.redhat.com with SMTP; 18 Oct 2002 16:17:02 -0000 Received: from [212.9.189.171] (helo=deneb.enyo.de) by mail.enyo.de with esmtp (Exim 3.34 #2) id 182Znx-00010S-00; Fri, 18 Oct 2002 18:16:53 +0200 Received: from fw by deneb.enyo.de with local (Exim 3.34 #4) id 182Zo3-0000LZ-00; Fri, 18 Oct 2002 18:16:59 +0200 To: dewar@gnat.com (Robert Dewar) Cc: berndtrog@yahoo.com, gcc@gcc.gnu.org Subject: Re: Ada/GNAT runtime library? References: <20021018161105.DED3AF28F4@nile.gnat.com> From: Florian Weimer Mail-Followup-To: dewar@gnat.com (Robert Dewar), berndtrog@yahoo.com, gcc@gcc.gnu.org Date: Fri, 18 Oct 2002 11:02:00 -0000 In-Reply-To: <20021018161105.DED3AF28F4@nile.gnat.com> (dewar@gnat.com's message of "Fri, 18 Oct 2002 12:11:05 -0400 (EDT)") Message-ID: <87n0pbrabo.fsf@deneb.enyo.de> User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-10/txt/msg01126.txt.bz2 dewar@gnat.com (Robert Dewar) writes: >> These are GNU libc bugs (or missing features) and should be fixed >> there. > No, that's quite wrong, on most targets the thread package is supplied > by the manufacturer it has nothing to do with GNU libc. I was talking about the GNU platforms, of course. autoconf-based portability to other GNU-supported architectures should be possible (if POSIX threads are provided by GNU libc), otherwise there is some portability problem which might not affect only GNAT, but a wider range of software. That's why I think these issues should be addressed in GNU libc, so that all applications can benefit. >> Timer frequencies? > > Just an example, the issue of how you know the timer frequency, whether > the timer has to be initialized etc. Ah, you can't get this information on Linux. It's shielded by the kernel. There are some traditional values for HZ on most architectures, but these values can change (and recently did on x86, AFAIK).