Re: Pros and cons of high-level intermediate languages

chased@rbbb.Eng.Sun.COM (David Chase)
Tue, 4 Aug 1992 23:21:57 GMT

          From comp.compilers

Related articles
[22 earlier articles]
Re: Pros and cons of high-level intermediate languages graham@maths.su.oz.au (1992-08-02)
Re: Pros and cons of high-level intermediate languages ridoux@irisa.fr (1992-08-04)
Re: Pros and cons of high-level intermediate languages kanze@us-es.sel.de (1992-08-04)
Re: Pros and cons of high-level intermediate languages boehm@parc.xerox.com (1992-08-03)
Re: Pros and cons of high-level intermediate languages rjbodkin@theory.lcs.mit.edu (Ronald Bodkin) (1992-08-04)
Re: Pros and cons of high-level intermediate languages optima!kwalker@cs.arizona.edu (1992-08-04)
Re: Pros and cons of high-level intermediate languages chased@rbbb.Eng.Sun.COM (1992-08-04)
Re: Pros and cons of high-level intermediate languages nfsun!gchamber@uunet.UU.NET (1992-08-04)
Re: Pros and cons of high-level intermediate languages moss@cs.umass.edu (1992-08-05)
Re: Pros and cons of high-level intermediate languages chased@rbbb.Eng.Sun.COM (1992-08-07)
Re: Pros and cons of high-level intermediate languages maniattb@cs.rpi.edu (1992-08-07)
Re: Pros and cons of high-level intermediate languages diamond@jit.dec.com (1992-08-10)
| List of all articles for this month |
Newsgroups: comp.compilers
From: chased@rbbb.Eng.Sun.COM (David Chase)
Organization: Sun Microsystems, Mt. View, Ca.
Date: Tue, 4 Aug 1992 23:21:57 GMT
Keywords: translator, design
References: 92-07-064 92-08-004

graham@maths.su.oz.au (Graham Matthews) writes:


>Now the argument appears to have shifted to one of performance. I agree
>that the peformance will be affected. My question is then whether the
>performance loss is due to C or due to using GC. Surely in the presence of
>GC one is always going to take a performance hit beacause the values of
>pointers can change at any time?


The short answer is "no". Note that garbage collection is a fairly rare
event, and thus special case code can be run in the event of a garbage
collection to translate to and from the optimized machine state. The
people at U Mass (Moss, Hudson, Diwanm, ??) are doing this for GNU
Modula-3.


Even so, the pointers need not move, but there can still be problems. The
trick here is to always keep at least one root pointer alive. I'll let
Hans elaborate on this, or I'll do it later; I've got work to do right
now.


>[Somebody suggested that it might be possible to define some extensions to
>C that would make it easier to garbage collect. Any thoughts? -John]


See above.


David Chase
Sun
--


Post a followup to this message

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