Re: Caller allocates space for callee-save registers

dalamb@qucis.queensu.ca (David Lamb)
Wed, 3 Jun 1992 14:08:12 GMT

          From comp.compilers

Related articles
[5 earlier articles]
Re: Caller allocates space for callee-save registers juul@diku.dk (1992-06-01)
Re: Caller allocates space for callee-save registers andrew@rentec.com (1992-06-01)
Re: Caller allocates space for callee-save registers stephen@estragon.uchicago.edu (1992-06-01)
Re: Caller allocates space for callee-save registers preston@dawn.cs.rice.edu (1992-06-01)
Re: Caller allocates space for callee-save registers leichter@zodiac.rutgers.edu (1992-06-02)
Re: Caller allocates space for callee-save registers pardo@cs.washington.edu (1992-06-03)
Re: Caller allocates space for callee-save registers dalamb@qucis.queensu.ca (1992-06-03)
Re: Caller allocates space for callee-save registers andrew@rentec.com (1992-06-03)
Re: Caller allocates space for callee-save registers preston@dawn.cs.rice.edu (1992-06-04)
Optimized cross-language interfaces scott@cs.rochester.edu (1992-06-04)
Re: Caller allocates space for callee-save registers pardo@cs.washington.edu (1992-06-04)
Re: Caller allocates space for callee-save registers andrew@rentec.com (1992-06-05)
Re: Caller allocates space for callee-save registers henry@zoo.toronto.edu (1992-06-05)
[3 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: dalamb@qucis.queensu.ca (David Lamb)
Keywords: registers, optimize, design
Organization: Computing & Information Science, Queen's University at Kingston
References: 92-05-123 92-06-013
Date: Wed, 3 Jun 1992 14:08:12 GMT

pardo@cs.washington.edu (David Keppel) writes:
>... I belive existing systems fail because they lack simple
>and useful facilities for managing types: identification, checking,
>conversion, and exchange. (David Lamb, is now probably either laughing or
>crying).


Well, actually, neither; I'm just sighing. Canadians of British descent
are too reserved to either laugh or cry in public.


But, seriously: (presuming David's referring to IDL and suchlike), perhaps
the main reason existing systems don't have such facilities is that I/we
didn't make it a priority to get a portable IDL subset out early, say back
in '83 while I was waiting for my committee to read my thesis. I'm not
sure why IDL derivatives aren't becoming more widespread now, though;
Scorpion (Rick Snodgrass' system) is in the public domain, and John
Nestor's Professional IDL and IDB (IDL-based persistent object store) are
commercial products.


I think there's a few articles on IDL in the comp.compilers archives.
As a quick summary of the most relevant information:


Richard Snodgrass
Department of Computer Science,
University of Arizona
Tucson, AZ 85721
rts@arizona.edu


%E Richard Snodgrass
%T The Interface Description Language: Definition and Use
%C Rockville, MD
%I Computer Science Press
%D 1989


John Nestor
75 West Chapel Ridge Road
Pittsburgh, PA 15238


%A John R. Nestor
%A Joseph M. Newcomer
%A Paola Giannini
%A Donald Stone
%T IDL: The Language and its Implementation
%I Prentice-Hall
%D 1990
--


Post a followup to this message

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