From: Abdullah Siddiqui <siddiquiabdullah92@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: C++ version for GCC development
Date: Mon, 7 Feb 2022 18:04:26 -0500 [thread overview]
Message-ID: <CADgxu+Q_0YYhy7=Z6Qe4Q8nnRfxVonzP1w7on1055y1c+FFZBQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRi1=nru=8aUGoYxnma5EY7HznaLM0P9BQBVv=-vQb_dQ@mail.gmail.com>
Hello Jonathan.
Thank you for the quick response.
I got 14% from the following GitHub page:
https://github.com/gcc-mirror/gcc
Am I not looking at the correct source for the GCC source code?
Waiting for your reply.
Regards,
Abdullah.
On Mon, Feb 7, 2022, 5:56 PM Jonathan Wakely, <jwakely.gcc@gmail.com> wrote:
>
>
> On Mon, 7 Feb 2022, 22:27 Abdullah Siddiqui via Gcc-help, <
> gcc-help@gcc.gnu.org> wrote:
>
>> Hello.
>>
>> This question is for the developers of GCC:
>>
>> Which C++ version are you using to write the C++ code of the current GCC
>> version?
>
>
>
> C++11
>
>
> Is only 14% of the current GCC codebase composed of C++ code?
>>
>
>
> Where do you get that number? It seems low.
>
>
>>
>>
next prev parent reply other threads:[~2022-02-07 23:04 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 [this message]
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
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='CADgxu+Q_0YYhy7=Z6Qe4Q8nnRfxVonzP1w7on1055y1c+FFZBQ@mail.gmail.com' \
--to=siddiquiabdullah92@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@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).