public inbox for
help / color / mirror / Atom feed
From: Eric Gallager <>
Subject: gcc-wwwdocs branch master updated. f4b4d0f783246dd6f58944cdb542446d5e7589d3
Date: Wed,  1 Dec 2021 17:24:23 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  f4b4d0f783246dd6f58944cdb542446d5e7589d3 (commit)
      from  185b965c66dfa899dc550b16ef1af33939d82e71 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit f4b4d0f783246dd6f58944cdb542446d5e7589d3
Author: Eric Gallager <>
Date:   Wed Dec 1 12:24:20 2021 -0500

    htdocs/projects/beginner.html: update list of large source files
    This also rewords the sentences after it to move away from the first person, and adds a shell command that can be used to regenerate the list of large files.

diff --git a/htdocs/projects/beginner.html b/htdocs/projects/beginner.html
index 589b47c8..5ad00ad8 100644
--- a/htdocs/projects/beginner.html
+++ b/htdocs/projects/beginner.html
@@ -135,25 +135,33 @@ to take those patches too.</p>
-	413K combine.c
-	408K dwarf2out.c
-	375K cp/pt.c
-	367K fold-const.c
-	356K loop.c
-	342K cp/decl.c
-	278K expr.c
-	238K cp/class.c
-	234K c-typeck.c
-	233K cse.c
-	231K c-decl.c
-	200K cp/typeck.c
-	168K function.c
+	1.4M	cp/parser.c
+	1000K	dwarf2out.c
+	932K	cp/pt.c
+	684K	c/c-parser.c
+	576K	cp/decl.c
+	516K	cp/
+	512K	fold-const.c
+	500K	gimplify.c
+	492K	c/c-typeck.c
+	484K	combine.c
+	460K	omp-low.c
+	432K	tree.c
+	408K	expr.c
+	404K	cp/call.c
-<p>There are several other files in this size range, which I have left
+<p>There are several other files in this size range, which are left
 out because touching them at all is unwise (reload, the Fortran front
-end).  You can try, but I am not responsible for any damage to your
-sanity which may result.</p>
+end).  You can try, but breaking them up likely may prove rather
+difficult, so beware of the level of challenge before attempting.</p>
+<p>Note that the list of large files in this section is generated with the
+following shell command, run from the gcc subdirectory:</p>
+	du -sh *.{c,h,cc} */*.{c,h,cc} | grep -v fortran | sort -hr | head -n 14
 <li>Remove as much code from parser actions as possible.


Summary of changes:
 htdocs/projects/beginner.html | 40 ++++++++++++++++++++++++----------------
 1 file changed, 24 insertions(+), 16 deletions(-)


                 reply	other threads:[~2021-12-01 17:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).