public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
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 19:17:29 -0500	[thread overview]
Message-ID: <CADgxu+T-kuEeFRGFmETdkY7veEceZuo5GP36C7oPYY9BwyzM2w@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRt5MU++teOUTL-Qf9es263x_czfvW=EzvOX=yPhpHhXQ@mail.gmail.com>

Jonathan,

Thank you for the clarification.

Can I still refer to the code in the GitHub repo for the latest source code
of GCC or is it obsolete?

Waiting for your reply.

Regards,
Abdullah.

On Mon, Feb 7, 2022, 6:35 PM Jonathan Wakely, <jwakely.gcc@gmail.com> wrote:

>
>
> On Mon, 7 Feb 2022 at 23:04, Abdullah Siddiqui <
> siddiquiabdullah92@gmail.com> wrote:
>
>> 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?
>>
>
> That's an unofficial mirror that's nothing to do with the GCC project, but
> it does have a copy of the right sources. Those numbers are wrong though.
> It counts several .h and .C files as C when they are C++. It's a rough
> estimate based on simple heuristics done automatically by GitHub. The true
> number is higher.
>
> It also looks like they haven't updated those numbers since April last
> year, so it will wrongly count all .c files as C even the ones which
> contain C++ instead. A huge number of files were renamed from .c to .cc
> recently, because they contain C++ and so had a misleading .c extension.
> That doesn't seem to be accounted for in those numbers.
>
>
>

  reply	other threads:[~2022-02-08  0:17 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 [this message]
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+T-kuEeFRGFmETdkY7veEceZuo5GP36C7oPYY9BwyzM2w@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).