public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Abdullah Siddiqui <siddiquiabdullah92@gmail.com>
Cc: Gabriel Ravier <gabravier@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: C++ version for GCC development
Date: Fri, 4 Mar 2022 09:13:01 +0000	[thread overview]
Message-ID: <CAH6eHdTg+ra3HafiKSyZD6MjBY02WAJQTRSm_r05MmVcrxS16g@mail.gmail.com> (raw)
In-Reply-To: <CADgxu+Qi=xC0LEEp0sAqbHxUjmX+Pvxay=4Rt2KdL0g4+BODiA@mail.gmail.com>

On Fri, 4 Mar 2022 at 03:07, Abdullah Siddiqui
<siddiquiabdullah92@gmail.com> wrote:
>
> Hello Jonathan.
>
> Thank you for the detailed clarification.
>
>> > At what point did the GCC developers give up C++98 and start using C++11?
>
>
>> For GCC 11. This is stated at https://gcc.gnu.org/install/prerequisites.html
>
>
> Are you referring to these lines:
>
>> ISO C++11 compiler
>> Necessary to bootstrap GCC.
>>
>>  Versions of GCC prior to 11 also allow bootstrapping with an ISO C++98 compiler,.....

Yes, those lines.

>
> I thought bootstrapping and compilation are two separate things. In this context, are bootstrapping and compilation the same i.e. GCC is a compiler and the ISO C++11 compiler is being used to compile GCC?

Yes, that's right.

In this context bootstrapping GCC means building it from source (which
includes compilation but also linking, and then repeating the whole
process using the just-built GCC to build itself again).

Since GCC 11, the first stage where you build GCC with a pre-existing
compiler must be done with a C++11 compiler. Before GCC 11 a C++98
compiler was needed.

>
>> The exceptions are some tests which have .c extensions but get
>> compiled as both C and C++, when we want to test that both language
>> front-ends pass the test.
>
>
> Are you referring to files in the testsuite folders (example: gcc/testsuite/g++.dg/lto/pr65302_1.C)?

See Xi Ruoyao's answer.

  parent reply	other threads:[~2022-03-04  9:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 22:26 Abdullah Siddiqui
2022-02-07 22:56 ` Jonathan Wakely
2022-02-07 23:04   ` Abdullah Siddiqui
2022-02-07 23:35     ` Jonathan Wakely
2022-02-08  0:17       ` Abdullah Siddiqui
2022-02-08  2:21         ` Gabriel Ravier
2022-02-08  2:42           ` Abdullah Siddiqui
2022-02-08  2:44             ` Abdullah Siddiqui
2022-02-08  7:49               ` Jonathan Wakely
2022-02-08 16:56                 ` Abdullah Siddiqui
2022-02-08 16:59                   ` Jonathan Wakely
2022-02-08 17:04                     ` Abdullah Siddiqui
2022-02-08 17:07                       ` Jonathan Wakely
2022-02-09  3:40                         ` Abdullah Siddiqui
2022-03-03  9:04                           ` Abdullah Siddiqui
2022-03-03 10:35                             ` Jonathan Wakely
2022-03-04  3:07                               ` Abdullah Siddiqui
2022-03-04  6:29                                 ` Xi Ruoyao
2022-03-04 23:01                                   ` Abdullah Siddiqui
2022-03-04  9:13                                 ` Jonathan Wakely [this message]
2022-03-04 23:03                                   ` Abdullah Siddiqui

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=CAH6eHdTg+ra3HafiKSyZD6MjBY02WAJQTRSm_r05MmVcrxS16g@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gabravier@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=siddiquiabdullah92@gmail.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).