Re: Is register stack compilers' friend?

jeremy@suede.sw.oz.au (Jeremy Fitzhardinge)
Mon, 13 Nov 1995 05:53:00 GMT

          From comp.compilers

Related articles
Is register stack compilers' friend? jaidi@technet.sg (1995-10-31)
Re: Is register stack compilers' friend? hbaker@netcom.com (1995-11-04)
Re: Is register stack compilers' friend? cliffc@ami.sps.mot.com (1995-11-05)
Re: Is register stack compilers' friend? stevec@pact.srf.ac.uk (1995-11-06)
Is register stack compilers' friend? dave@occl-cam.demon.co.uk (Dave Lloyd) (1995-11-06)
Re: Is register stack compilers' friend? paulb@pablo.taligent.com (1995-11-09)
Re: Is register stack compilers' friend? jeremy@suede.sw.oz.au (1995-11-13)
| List of all articles for this month |
Newsgroups: comp.compilers
From: jeremy@suede.sw.oz.au (Jeremy Fitzhardinge)
Keywords: architecture, bibliography
Organization: Softway Pty Limited
References: 95-11-026 95-11-050
Date: Mon, 13 Nov 1995 05:53:00 GMT

hbaker@netcom.com (Henry Baker) writes:
>Phil Koopman, who was at CMU and now at United Technologies, did some
>studies on high performance implementations of C on a stack machine.
>Unfortunately, I don't recall the exact reference.


@article{KoopmanPhi1992a,
  author ="Koopman, Philip",
  title ="A Preliminary Exploration of Optimized Stack Code Generation",
  journal ="Journal of Forth Applications and Research",
  number ="4",
  volume ="6",
  year ="1992",
  scope ="gen",
  abstractURL ="http://utrcwww.utc.com/cgi-bin/utrcdocsearch",
  documentURL ="http://utrcwww.utc.com/UTRC/Techreports/koopman.ps",
  keywords ="intra-block stack scheduling"
}


I don't know if he ever published anything beyond the "Preliminary
Exploration". His results were quite interesting: given a reasonable
set of native stack operations, you could systematically eliminate a
lot of register variables in favor of stack use within basic blocks.
He said he didn't find as satisfactory solution for global register
elimination.


J
--


Post a followup to this message

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