From ... From: Erik Naggum Subject: Re: Garbage collection cost (was Re: Parenthesized syntax challenge) Date: 1995/10/29 Message-ID: <19951029T012233Z@naggum.no>#1/1 X-Deja-AN: 118281344 references: <44aa9a$j5h@miso.cs.uq.edu.au> <45ksdk$7gr@jive.cs.utexas.edu> <46jb8v$sm8@news.parc.xerox.com> <46rkuv$jh8@news.parc.xerox.com> organization: Naggum Software; +47 2295 0313 newsgroups: comp.lang.dylan,comp.lang.lisp,comp.lang.java [Henry Baker] | I would advise using .-relative addressing for all pointers (perhaps | some C compiler vendor/GNU is listening), and start using VM | compression. [Hans Boehm] | Please don't do that for C; you'll break conservative GC completely. | (You'll also break at least all C code that calls third party | libraries, and I doubt you'll have an ANSI conforming compiler. How do | you handle union assignments? But I have my priorities straight :-)) this is odd. to build shared objects (libraries) under, e.g., SunOS 4, so-called "position-independent code" must be emitted by the assembler, and special considerations must be followed by the compiler. (not all C code can be compiled into shared objects, but I don't know what the conditions are.) given this, are you saying that shared objects would cause the compiler (or library) not to be conforming to ANSI C? if so, this is, IMNSHO, a problem in the standard (ISO C, actually) that should be fixed. # -- a good picture may well be worth a thousand words, but on the WWW, even bad imagemaps cost tens of thousands of words.