From: Diego Novillo <dnovillo@google.com>
To: gcc-patches@gcc.gnu.org
Cc: gchare@google.com, crowl@google.com
Subject: [wwwdocs] Document new pth-icm branch
Date: Fri, 03 Jun 2011 14:03:00 -0000 [thread overview]
Message-ID: <20110603140252.GA4310@google.com> (raw)
Since we are not sure whether pre-tokenized headers are worth
adding at all (the performance gains are minimal), Gabriel has
started removing that code and the parser instrumentation code we
had in the pph branch.
This will simplify branch maintenance wrt merges, but we are
still not sure whether we will do anything with PTH. So, I have
created a sub-branch (pth-icm) to hold that code for now.
This patch adds documentation for it.
Committed to wwwdocs.
Diego.
Index: svn.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v
retrieving revision 1.161
diff -u -d -u -p -r1.161 svn.html
--- svn.html 27 Apr 2011 14:51:51 -0000 1.161
+++ svn.html 3 Jun 2011 13:58:10 -0000
@@ -495,6 +495,18 @@ the command <code>svn log --stop-on-copy
href="mailto:crowl@google.com">Lawrence Crowl</a>. Patches should be
prefixed with <code>[pph]</code> in the subject line.</dd>
+ <dt>pth-icm</dt>
+ <dd>This is a sub-branch of the <code>pph</code> branch. It
+ implements
+ <a href="http://gcc.gnu.org/wiki/pph#Pre-Tokenized_Headers_.28PTH.29">
+ Pre-Tokenized Headers for C++</a>. Additionally, it contains
+ instrumentation code in the C++ parser that was used in an
+ incremental compiler model (icm) to study the effects of an
+ incremental compiler cache for a compiler server. The branch is
+ maintained by <a href="mailto:dnovillo@google.com">Diego Novillo</a>
+ and <a href="mailto:crowl@google.com">Lawrence Crowl</a>. Patches
+ should be prefixed with <code>[pph]</code> in the subject line.</dd>
+
</dl>
<h3 id="distrobranches">Distribution Branches</h3>
reply other threads:[~2011-06-03 14:03 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:
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=20110603140252.GA4310@google.com \
--to=dnovillo@google.com \
--cc=crowl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gchare@google.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).