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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,fc35bf7ba6fca42d
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!l41g2000cwc.googlegroups.com!not-for-mail
From: "fabio de francesco" <fmdf@tiscali.it>
Newsgroups: comp.lang.ada
Subject: Re: "new" word
Date: 16 Mar 2005 05:01:29 -0800
Organization: http://groups.google.com
Message-ID: <1110978089.521428.75690@l41g2000cwc.googlegroups.com>
References: <1110966980.482176.111570@f14g2000cwb.googlegroups.com>
   <3297984.Y1VDRVLb6y@jellix.jlfencey.com>
   <slrnd3g58c.r83.adi@ppc201.mipool.uni-jena.de>
NNTP-Posting-Host: 82.49.51.212
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1110978094 25891 127.0.0.1 (16 Mar 2005 13:01:34
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 16 Mar 2005 13:01:34 +0000 (UTC)
In-Reply-To: <slrnd3g58c.r83.adi@ppc201.mipool.uni-jena.de>
User-Agent: G2/0.2
Complaints-To: groups-abuse@google.com
Injection-Info: l41g2000cwc.googlegroups.com; posting-host=82.49.51.212;
   posting-account=Lp02jQ0AAABMd3TAghNf0TM2YBZqD_JE
Xref: g2news1.google.com comp.lang.ada:9476
Date: 2005-03-16T05:01:29-08:00
List-Id: <comp.lang.ada>


Adrian Knoth wrote:
> Vinzent 'Gadget' Hoefler <nntp-2005-03@t-domaingrabbing.de> wrote:
>
> [new via malloc of libc]
> > so why should one write an Ada specific memory allocator that
>
> To get rid of libc, C and all this? ;) A native kernel interface
> would be nice to eliminate possible implementation errors in libc.
>
> On the other hand as far as I can see there is no binary
representation
> of the linux-kernel, in other words, you'll need to dynamically
> adapt the Ada memory layout to the corresponding kernel (+compiler).

No, it isn't required. You don't need a Kernel-ABI in order to access
system calls in kernel space, as I wrote in another post in this
thread. There is a standardised way to access syscalls through
interrupt H80.

Imagine you write a new syscall in Linux kernel and you want to use it
before it is binded into the LibC, you can do it with some simple
Assembly inline C/C++/Ada and whatever else programming language.

Same way you can access sys_sbrk() that is the standard syscall that
provide memory in user space.

fabio de francesco


>
> Another way would be to specify the Kernel-ABI, but I don't expect
> this to happen earlier than Hurd ;)
>
> AdaOS would probably come along with a well-defined ABI and no
> libc, but libada.
>
>
> --
> mail: adi@thur.de  	http://adi.thur.de	PGP: v2-key via keyserver
> 
> Mit leerem Kopf nickt es sich leichter.