Re: A C compiler written in C targeting C

eclectictech@usa.net (Sebastiano Pilla)
28 Mar 1999 17:06:13 -0500

          From comp.compilers
Related articles
A C compiler written in C targeting C dg@tao.co.uk (1999-03-23)
Re: A C compiler written in C targeting C mikee@cetasoft.cog (1999-03-28)
Re: A C compiler written in C targeting C kadhim@lucent.com (Basim Kadhim) (1999-03-28)
Re: A C compiler written in C targeting C nshaf@intur.net (Nick Shaffner) (1999-03-28)
Re: A C compiler written in C targeting C dmk42@my-dejanews.com (1999-03-28)
Re: A C compiler written in C targeting C derek@knosof.co.uk (1999-03-28)
Re: A C compiler written in C targeting C eclectictech@usa.net (1999-03-28)
Re: A C compiler written in C targeting C dg@tao.co.uk (1999-04-01)
Re: A C compiler written in C targeting C zalman@netcom.com (1999-04-03)
Re: A C compiler written in C targeting C gillga@ilk.de (1999-05-16)
| List of all articles for this month |
From: eclectictech@usa.net (Sebastiano Pilla)
Newsgroups: comp.compilers
Date: 28 Mar 1999 17:06:13 -0500
Organization: eclectic technologies
References: 99-03-067
Keywords: C, storage

David Given <dg@tao.co.uk> wrote:


> I have an operating system with strange memory semantics (GEOS, if
> you're interested). Blocks of memory may move at any time unless
> locked down. You're not supposed to leave blocks locked. You refer to
> blocks by their handles.


> [MacOS does sort of the same thing, maybe there's some hackery there. -John]


If GEOS cannot give non-relocatable blocks, then I doubt that the
solutions used by Mac OS C compilers can help you: usually they grab a
pool of memory, then subdivide it to fulfill 'malloc'
requests. However that initial pool is already non-relocatable, and
accessed thru single pointer dereferences.


Regards
Sebastiano Pilla

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.