Related articles |
---|
Writing a C++ compiler in C++ for-usenet-5c@alicewho.com (Adem) (2008-10-27) |
Re: Writing a C++ compiler in C++ DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-10-28) |
Re: Writing a C++ compiler in C++ echristo@gmail.com (Eric Christopher) (2008-10-28) |
Re: Writing a C++ compiler in C++ cfc@shell01.TheWorld.com (Chris F Clark) (2008-10-28) |
Re: Writing a C++ compiler in C++ marcov@stack.nl (Marco van de Voort) (2008-10-30) |
Re: Writing a C++ compiler in C++ DrDiettrich1@aol.com (Hans-Peter Diettrich) (2008-10-31) |
Re: Writing a C++ compiler in C++ marcov@stack.nl (Marco van de Voort) (2008-11-01) |
From: | Marco van de Voort <marcov@stack.nl> |
Newsgroups: | comp.compilers |
Date: | Thu, 30 Oct 2008 16:33:05 +0000 (UTC) |
Organization: | Stack Usenet News Service |
References: | 08-10-049 08-10-050 |
Keywords: | practice |
Posted-Date: | 31 Oct 2008 10:16:39 EDT |
On 2008-10-28, Hans-Peter Diettrich <DrDiettrich1@aol.com> wrote:
>
> Most C++ compilers are based on C, because it's hard enough to make C
> programs run on multiple platforms. Using C++ will increase that
> incompatibility again.
>
> AFAIK gcc will be compiled three times, until the compiler is usable on
> a different platform. The bootstrap process uses the C compiler of the
> platform for the first compilation, then the created compiler to compile
> itself in a restricted version, and that compiler to produce the final
> version. Unless you restrict your project to compile with one specific
> C++ compiler, you'll have to bootstrap your compiler in a similar way.
(an alternate to dump such bootstrap strategy, and aim more for
crosscompiling)
Return to the
comp.compilers page.
Search the
comp.compilers archives again.