Re: Pros and cons of high-level intermediate languages

Ronald Bodkin <rjbodkin@theory.lcs.mit.edu>
Tue, 4 Aug 1992 04:25:09 GMT

          From comp.compilers

Related articles
[20 earlier articles]
Re: Pros and cons of high-level intermediate languages moss@cs.umass.edu (1992-07-30)
Re: Pros and cons of high-level intermediate languages boehm@parc.xerox.com (1992-07-30)
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)
[1 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: Ronald Bodkin <rjbodkin@theory.lcs.mit.edu>
Organization: MIT Lab for Computer Science
Date: Tue, 4 Aug 1992 04:25:09 GMT
Keywords: performance, storage
References: 92-07-064 92-08-004

graham@maths.su.oz.au (Graham Matthews) writes:
      ... Your translator should have compiled the loop into


for( i = 0; i < 100; i++ )
object_access(p)[i] = object_access(q)[i];
      ...


      You take a performance hit here but in the presence of GC surely you have
      to take that hit no matter what IL you use?


This is simply untrue. In the presence of GC, you can STILL store
pointers that are part of the "seed" for live data in registers. The
problem is that C optimizers don't consider such a use of registers. If
you go to assembly output, you certainly can use registers and (safely)
garbage collect.


Ron
--


Post a followup to this message

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