From: Alexandre Oliva <aoliva@redhat.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: mark@codesourcery.com, gcc@gcc.gnu.org, gdr@integrable-solutions.net
Subject: Re: Converting to ISO C89
Date: Sun, 06 Apr 2003 02:11:00 -0000 [thread overview]
Message-ID: <or8yuopmoo.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <200303251752.MAA08671@caip.rutgers.edu>
On Mar 25, 2003, "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> wrote:
> IMHO once we've decided to require ISO C89 to bootstrap, we should
> remove gcc-isms from the cp/ dir and compile cc1plus during stage1.
> We can perhaps condition cc1plus during stage1 iff java is enabled.
> Then java (and all other) frontends can use C++ wherever it makes
> sense.
It's not that simple, unfortunately. Without libstdc++, there's not
much of C++ any language can possibly use.
/me thinks if we're to use C++ in the compiler, it makes more sense to
require a complete, functional C++ compiler upfront, and use it in all
stages.
At least until we've moved the bootstrap process to the top-level, and
arrange for C++ programs created by each stage to be runnable in the
build tree, this is the best way to proceed. Unless we use libtool to
link such executables or set LD_LIBRARY_PATH so that each stage's C++
libraries are found, they won't run. And I realize most people won't
like the notion of bringing libtool into the gcc/ build machinery,
so...
Well, I thought it was worth pointing out, even if a bit late :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2003-04-05 23:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 7:12 Mark Mitchell
2003-03-25 12:12 ` Gabriel Dos Reis
2003-03-25 17:38 ` Mark Mitchell
2003-03-25 18:25 ` Kaveh R. Ghazi
2003-03-25 20:38 ` Raja R Harinath
2003-03-25 21:55 ` Zack Weinberg
2003-03-25 22:02 ` Falk Hueffner
2003-03-25 22:17 ` Zack Weinberg
2003-03-25 22:25 ` Falk Hueffner
2003-03-26 9:19 ` Gabriel Dos Reis
2003-03-26 0:05 ` Joe Buck
2003-03-26 6:56 ` Zack Weinberg
2003-03-25 22:13 ` Raja R Harinath
2003-03-25 22:23 ` tm_gccmail
2003-03-25 22:26 ` Joe Buck
2003-03-25 22:40 ` Raja R Harinath
2003-03-26 8:49 ` Gabriel Dos Reis
2003-03-26 9:55 ` Zack Weinberg
2003-04-06 2:11 ` Alexandre Oliva [this message]
2003-04-06 2:46 ` Zack Weinberg
2003-04-06 2:47 ` Alexandre Oliva
2003-04-06 3:15 ` Kaveh R. Ghazi
2003-04-06 4:40 ` Geoff Keating
2003-04-06 16:23 ` Kaveh R. Ghazi
2003-03-30 12:45 ` Gabriel Dos Reis
2003-03-31 5:17 ` Mark Mitchell
2003-04-03 1:06 ` Zack Weinberg
2003-04-12 17:59 ` Gabriel Dos Reis
2003-04-12 18:06 ` Kaveh R. Ghazi
2003-04-10 15:31 ` Andrew Haley
2003-04-10 16:42 ` Mark Mitchell
2003-04-12 19:32 ` Gabriel Dos Reis
2003-04-14 11:21 ` Mark Mitchell
2003-04-14 12:57 ` Andrew Haley
2003-04-16 10:42 ` Andrew Haley
2003-04-16 17:25 ` Kaveh R. Ghazi
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=or8yuopmoo.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=ghazi@caip.rutgers.edu \
--cc=mark@codesourcery.com \
/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).