public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: dewar@gnat.com (Robert Dewar)
Cc: berndtrog@yahoo.com,  gcc@gcc.gnu.org
Subject: Re: Ada/GNAT runtime library?
Date: Fri, 18 Oct 2002 11:02:00 -0000	[thread overview]
Message-ID: <87n0pbrabo.fsf@deneb.enyo.de> (raw)
In-Reply-To: <20021018161105.DED3AF28F4@nile.gnat.com> (dewar@gnat.com's message of "Fri, 18 Oct 2002 12:11:05 -0400 (EDT)")

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).

  reply	other threads:[~2002-10-18 16:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 11:00 Robert Dewar
2002-10-18 11:02 ` Florian Weimer [this message]
2002-10-20 22:16   ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2002-10-18 15:34 Bernd Trog
2002-10-18  9:49 Robert Dewar
2002-10-18 10:39 ` Florian Weimer
2002-10-18 10:41   ` Arnaud Charlet
2002-10-18  9:10 Robert Dewar
2002-10-18  9:44 ` Joel Sherrill
2002-10-18  8:56 Robert Dewar
2002-10-18 15:47 ` Bernd Trog
2002-10-18  8:34 Robert Dewar
2002-10-18  9:17 ` Robert Dewar
2002-10-18 15:54 ` Bernd Trog
2002-10-18  8:27 Robert Dewar
2002-10-18  8:56 ` Robert Dewar
2002-10-18  8:21 Robert Dewar
2002-10-18  4:21 Robert Dewar
2002-10-18  7:21 ` Bernd Trog
2002-10-18  0:06 Robert Dewar
2002-10-18  6:23 ` Bernd Trog
2002-10-18  7:28   ` Joel Sherrill
2002-10-17 17:31 Robert Dewar
2002-10-17 17:10 Robert Dewar
2002-10-17 22:18 ` Bernd Trog
2002-10-18  9:27   ` Florian Weimer
2002-10-18  5:29 ` Andris Pavenis
2002-10-17 14:38 Bernd Trog
2002-10-17 15:00 ` Geert Bosch
2002-10-17 15:21   ` Bernd Trog
2002-10-17 15:48     ` Geert Bosch
2002-10-17 20:13       ` Bernd Trog

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87n0pbrabo.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=berndtrog@yahoo.com \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).