This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Converting the gcc backend to a library?
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Subject: Re: Converting the gcc backend to a library?
- From: Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>
- Date: 10 Jan 2000 11:09:34 -0200
- Cc: jamie dot lokier at cern dot ch, gcc at gcc dot gnu dot org
- References: <10001101314.AA13803@vlsi1.ultra.nyu.edu>
On Jan 10, 2000, kenner@vlsi1.ultra.nyu.edu (Richard Kenner) wrote:
> Not so. Consider a dynamic compilation environment such as Java,
> Guile, Perl or even Emacs Lisp if such things were that easy. Every
> interpreter-come-compiler uses an instance of the shared library.
> Yes, I do understand that. But my point is that in today's
> single-user workstation environment, how many processes that actually
> would use the GCC shared library would actually be simultaneously
> running in practice? I still believe that number is very small and
> only rarely over one.
Think of a Web server running multiple CGI scripts written in Perl,
Python, Guile, whatever, plus Java servlets. If all of these
environments could be linked with the same JIT compiler shared
library, wouldn't it be just great?
Of course, in the *current* state of affairs, you'd have little, if
any, sharing of code. But this can change if we help them change.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them