From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: richard.earnshaw@arm.com
Cc: rms@gnu.org, kenner@vlsi1.ultra.nyu.edu, gcc2@cygnus.com,
egcs@cygnus.com, rearnsha@arm.com
Subject: Re: Proposal for new organization of gcc
Date: Thu, 22 Jan 1998 02:29:00 -0000 [thread overview]
Message-ID: <orafcpeiq5.fsf@amazonas.dcc.unicamp.br> (raw)
In-Reply-To: <199801211057.KAA02749@sun52.NIS.cambridge>
Richard Earnshaw writes:
> Perhaps one solution for the multiple sub-libraries problem is for the
> build/install process to merge any existing libgcc.a with the new
> functions that are required, creating a single super-library that contains
> support routines for all the installed compilers.
This doesn't sound right to me. Changing libraries that are installed
already seems a bad idea to me. Installing multiple libraries, OTOH,
does not seem a big problem, IMHO.
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
next prev parent reply other threads:[~1998-01-22 2:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9801082336.AA26988@vlsi1.ultra.nyu.edu>
1998-01-08 16:24 ` Alexandre Oliva
1998-01-08 18:28 ` Michael Gschwind
1998-01-11 18:24 ` Richard Stallman
1998-01-11 18:58 ` Alexandre Oliva
1998-01-12 17:55 ` Richard Stallman
1998-01-13 4:31 ` Alexandre Oliva
1998-01-20 12:42 ` Richard Stallman
1998-01-20 14:54 ` Alexandre Oliva
1998-01-21 9:18 ` Richard Stallman
1998-01-22 1:45 ` Richard Earnshaw
1998-01-22 2:29 ` Alexandre Oliva [this message]
1998-01-22 4:12 ` Richard Earnshaw
1998-01-22 2:29 ` Alexandre Oliva
1998-01-23 14:48 ` Harvey J. Stein
1998-01-23 14:48 ` amylaar
[not found] <9801121156.AA07482@vlsi1.ultra.nyu.edu>
1998-01-12 4:09 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=orafcpeiq5.fsf@amazonas.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=rearnsha@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).