Related articles |
---|
ADA/C++ Compatibility problems dasilvia@sonalysts.com (1995-08-18) |
Re: ADA/C++ Compatibility problems papayd@gtewd.mtv.gtegsc.com (Dave Papay M/S 7G32 x2791) (1995-08-21) |
Re: ADA/C++ Compatibility problems bobduff@world.std.com (1995-08-21) |
Re: ADA/C++ Compatibility problems stachour@klondike.winternet.com (1995-08-25) |
Re: ADA/C++ Compatibility problems jan@neuroinformatik.ruhr-uni-bochum.de (1995-08-30) |
Re: ADA/C++ Compatibility problems gbaker@rp.CSIRO.AU (1995-09-07) |
Re: ADA/C++ Compatibility problems jan@neuroinformatik.ruhr-uni-bochum.de (1995-09-07) |
Re: ADA/C++ Compatibility problems leichter@zodiac.rutgers.edu (1995-09-07) |
Re: ADA/C++ Compatibility problems przemek@rrdjazz.nist.gov (1995-09-13) |
Re: ADA/C++ Compatibility problems jbuck@Synopsys.COM (1995-09-17) |
Re: ADA/C++ Compatibility problems leichter@zodiac.rutgers.edu (1995-09-21) |
Newsgroups: | comp.compilers |
From: | jan@neuroinformatik.ruhr-uni-bochum.de (Jan Vorbrueggen) |
In-Reply-To: | jan@neuroinformatik.ruhr-uni-bochum.de's message of Wed, 30 Aug 1995 11:22:44 GMT |
Keywords: | architecture, comment |
Organization: | Institut fuer Neuroinformatik, Ruhr-Universitaet Bochum, Germany |
References: | 95-08-127 95-08-189 95-09-031 |
Date: | Thu, 7 Sep 1995 13:28:44 GMT |
Our moderator comments on VMS' calling conventions:
[I gather there are (were?) performance problems -- the heavyweight CALLS
and CALLG instructions used in the common calling sequence were complicated
and slow. -John]
But those are artefacts of the VAX implementation. What I wanted to point out
is that VMS bothered to define a calling convention (including argument
passing mechanisms) and held both its own public interfaces and all compilers
to it. Most of the language manuals I've read also gave hints and examples to
explain and overcome the idiosyncrasies of languages in inter-language
calls. I'm sure that VMS on AXP does the same, without the CALL(S|G) slowdown.
Jan
[Good point. For that matter, OS/360 had a common calling sequence that was
reasonably fast and made it possible to intercall among Fortran, Cobol, and
PL/I. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.