From: Richard Earnshaw <rearnsha@arm.com>
To: rms@gnu.org
Cc: rearnsha@arm.com
Subject: Re: Proposal for new organization of gcc
Date: Thu, 22 Jan 1998 01:45:00 -0000 [thread overview]
Message-ID: <199801211057.KAA02749@sun52.NIS.cambridge> (raw)
In-Reply-To: <199801210803.BAA07127@wijiji.santafe.edu>
> This won't work. gcc needs cc1 in order to build libgcc.a,
>
> That's true. In fact, I think this is a show-stopper: unless we make
> it possible to compile libgcc2.c with whatever C compiler you use to
> compile GCC (not easy since it uses GCC features), we can't possibly
> support building other languages without C. We could perhaps make it
> work to compile libgcc2.c using C++, if you don't build the C
> compiler, but what if you choose to build only Fortran, Pascal or Ada?
>
Currently currently libgcc.a contains a range of functions for different
roles. Some are to support the core compiler (back end), eg functions to
support primitive operations such as division (eg divsi) and some are
language specific, like __eprintf (mainly for C's assert) or __builtin_new
(C++).
I don't think it is feasible to build the core compiler functions without
a gcc (though a native CC is also needed on many platforms for libgcc1
functions), but it shouldn't be necessary to build a completely new gcc to
compile these if gcc is already installed on the machine.
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 would certainly be
possible with Unix archive libraries, and probably most other OS's. It
wouldn't work if libgcc were made into a shared library, but there are
probably other issues there as well.
next prev parent reply other threads:[~1998-01-22 1:45 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 [this message]
1998-01-22 2:29 ` Alexandre Oliva
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=199801211057.KAA02749@sun52.NIS.cambridge \
--to=rearnsha@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).