From: "H.J. Lu" <hjl.tools@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: PATCH RFA: Build stages 2 and 3 with C++
Date: Wed, 20 Jul 2011 01:15:00 -0000 [thread overview]
Message-ID: <CAMe9rOoaCxJxGk-q6hAUq7KkWeP0GvuZH3mHnxHd0uF=bdkoKg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOrp8d42pybpgU+N0UKDjscQo_tO=uBQaNig4vbO3ePwRg@mail.gmail.com>
On Tue, Jul 19, 2011 at 5:26 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Tue, Jul 19, 2011 at 11:33 AM, Ian Lance Taylor <iant@google.com> wrote:
>> Ian Lance Taylor <iant@google.com> writes:
>>
>>> I would like to propose this patch as a step toward building gcc using a
>>> C++ compiler. This patch builds stage1 with the C compiler as usual,
>>> and defaults to building stages 2 and 3 with a C++ compiler built during
>>> stage 1. This means that the gcc installed and used by most people will
>>> be built by a C++ compiler. This will ensure that gcc is fully
>>> buildable with C++, while retaining the ability to bootstrap with only a
>>> C compiler, not a C++ compiler. This will permit us to experiment with
>>> optionally using C++ for some code, using a #ifdef to select the C
>>> implementation or the C++ implementation.
>>>
>>> I would suggest that we consider releasing 4.7 this way, as a small
>>> trial for building gcc with C++.
>>>
>>> This is a big step, so I am sending the patch to both gcc@ and
>>> gcc-patches@ for comments.
>>>
>>> Bootstrapped and ran testsuite on x86_64-unknown-linux-gnu.
>>>
>>> Ian
>>>
>>>
>>> 2011-07-15 Ian Lance Taylor <iant@google.com>
>>>
>>> * configure.ac: Add --enable-build-poststage1-with-cxx. If set,
>>> make C++ a boot_language. Set and substitute
>>> POSTSTAGE1_CONFIGURE_FLAGS.
>>> * Makefile.tpl (POSTSTAGE1_CONFIGURE_FLAGS): New variable.
>>> (STAGE[+id+]_CONFIGURE_FLAGS): Add $(POSTSTAGE1_CONFIGURE_FLAGS).
>>> * configure, Makefile.in: Rebuild.
>>
>>
>> I got agreement from two global reviewers and no objections.
>>
>> I have committed this patch.
>>
>> Please let me know about any problems.
>
> It caused:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49787
It also caused:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49786
--
H.J.
next prev parent reply other threads:[~2011-07-20 0:46 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 6:56 Ian Lance Taylor
2011-07-16 7:05 ` Andrew Pinski
2011-07-16 7:48 ` Ian Lance Taylor
2011-07-16 7:59 ` Basile Starynkevitch
2011-07-17 3:17 ` Ian Lance Taylor
2011-07-16 16:11 ` Diego Novillo
2011-07-16 22:58 ` Ian Lance Taylor
2011-07-17 10:36 ` Richard Guenther
2011-07-17 12:21 ` Eric Botcazou
2011-07-17 16:55 ` Richard Guenther
2011-07-17 17:55 ` Markus Trippelsdorf
2011-07-17 22:37 ` Markus Trippelsdorf
2011-09-04 17:20 ` Thomas Schwinge
2011-07-16 20:40 ` Toon Moene
2011-07-19 21:33 ` Ian Lance Taylor
2011-07-19 22:24 ` Gabriel Dos Reis
2011-07-20 0:46 ` H.J. Lu
2011-07-20 1:15 ` H.J. Lu [this message]
2011-07-20 6:28 ` David Edelsohn
2011-07-20 9:34 ` Jonathan Wakely
2011-07-20 11:02 ` Jonathan Wakely
2011-07-20 12:41 ` David Edelsohn
2011-07-20 12:48 ` Richard Guenther
2011-07-20 14:07 ` Diego Novillo
2011-07-20 14:34 ` Ian Lance Taylor
2011-07-20 15:35 ` Jonathan Wakely
2011-07-20 15:06 ` Toon Moene
2011-07-20 15:23 ` Ian Lance Taylor
2011-07-20 15:53 ` David Edelsohn
2011-07-20 15:55 ` Ian Lance Taylor
2011-07-20 20:05 ` David Edelsohn
2011-07-20 20:53 ` Ian Lance Taylor
2011-07-20 21:06 ` Mike Stump
2011-07-21 0:10 ` Ian Lance Taylor
2011-07-21 9:40 ` Basile Starynkevitch
2011-07-21 16:06 ` Ian Lance Taylor
2011-07-21 17:44 ` Jakub Jelinek
2011-07-21 19:40 ` Ian Lance Taylor
2011-07-21 20:12 ` Basile Starynkevitch
2011-07-21 22:38 ` Ian Lance Taylor
2011-07-21 6:57 ` David Edelsohn
2011-07-21 7:25 ` Eric Botcazou
2011-07-21 14:24 ` David Edelsohn
2011-07-20 17:58 ` Thomas Schwinge
2011-07-20 21:41 ` Toon Moene
2011-07-31 23:20 ` Marc Glisse
2011-08-01 9:14 ` Richard Guenther
2011-08-01 9:53 ` Joseph S. Myers
2011-08-01 9:59 ` Richard Guenther
2011-08-01 10:05 ` Marc Glisse
2011-08-08 17:42 ` Romain Geissler
2011-08-08 18:49 ` Ian Lance Taylor
2011-08-08 19:40 ` Romain Geissler
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='CAMe9rOoaCxJxGk-q6hAUq7KkWeP0GvuZH3mHnxHd0uF=bdkoKg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.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).