Re: Java virtual machine as target language for C/C++

Dave Love <d.love@daresbury.ac.uk>
13 Jun 1996 18:03:19 -0400

          From comp.compilers

Related articles
[21 earlier articles]
Re: Java virtual machine as target language for C/C++ robison@kai.com (Arch Robison) (1996-05-21)
Re: Java virtual machine as target language for C/C++ pardo@cs.washington.edu (1996-05-24)
Re: Java virtual machine as target language for C/C++ wws@renaissance.cray.com (1996-05-25)
Re: Java virtual machine as target language for C/C++ tmb@best.com (1996-05-26)
Re: Java virtual machine as target language for C/C++ dw3u+@andrew.cmu.edu (Daniel C. Wang) (1996-05-27)
Re: Java virtual machine as target language for C/C++ dave@occl-cam.demon.co.uk (Dave Lloyd) (1996-06-08)
Re: Java virtual machine as target language for C/C++ d.love@daresbury.ac.uk (Dave Love) (1996-06-13)
Re: Java virtual machine as target language for C/C++ bos@serpentine.com (1996-06-14)
Re: Java virtual machine as target language for C/C++ cdg@nullstone.com (1996-06-21)
compilation to C [was Re: Java virtual machine...] d.love@daresbury.ac.uk (Dave Love) (1996-06-23)
Optimization of Uncommon Code (Was Java ByteCode ...) dlmoore@ix.netcom.com (1996-06-30)
Re: Optimization of Uncommon Code (Was Java ByteCode ...) wws@renaissance.cray.com (Walter Spector) (1996-07-01)
Re: Optimization of Uncommon Code dwight@pentasoft.com (Dwight VandenBerghe) (1996-07-02)
[2 later articles]
| List of all articles for this month |

From: Dave Love <d.love@daresbury.ac.uk>
Newsgroups: comp.compilers
Date: 13 Jun 1996 18:03:19 -0400
Organization: Daresbury Laboratory, Warrington WA4 4AD, UK
References: 96-05-061 96-05-163 96-06-016
Keywords: UNCOL, C

Dave Lloyd <dave@occl-cam.demon.co.uk> writes:


  >> I'm surprised no one has mentioned C as a resonably sucessful
  >> multi-langauge multi-target UNCOL. f2c,p2c,m2c, Scheme->C, sml2c,
  >> Mercury, ghc, .... all


[Siskind's Stalin compiler for Scheme is allegedly particularly
notable in that class.]


  Dave> As illustration, g77 produces substantially better code than f2c+gcc.


Bad example, I think. In fact, it's only recently that g77 has caught
up with f2c+gcc in some areas (and should now mostly do at least as
well unless you can win by tricks like inlining library routines with
f2c). Also, my experience of f2c with gcc is that it hasn't been
substantially slower than the vendor compiler on the platforms I've
used (specifically MIPS), though I doubt that's true generally.


I'm sure there's room for improvement, however, particularly if the
facility to use Fortran no-alias semantics is added to the gcc
backend, as it may be.


Are meaningful comparisons available from compilers which can both
generate native code and go via C (GHC and Gambit, perhaps)?


--


Post a followup to this message

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