public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: danscox@mindspring.com To: gcc-gnats@gcc.gnu.org Subject: other/7233: provide ccache (see freshmeat.net) withing the gcc suite Date: Mon, 08 Jul 2002 08:26:00 -0000 [thread overview] Message-ID: <20020708152158.24720.qmail@sources.redhat.com> (raw) >Number: 7233 >Category: other >Synopsis: provide ccache (see freshmeat.net) withing the gcc suite >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: support >Submitter-Id: net >Arrival-Date: Mon Jul 08 08:26:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Daniel S. Cox >Release: Whenever is convienient >Organization: >Environment: ALL >Description: ccache is a seperate program that saves the .o files (and any stderr messages) from gcc -c. It forms an MD4 hash of the input file contents, the gcc driver size and mtime), and keeps the resultant files in a cache. On a later run, if an input files MD4 hash matches an extant file in the cache, that file is hard linked (if possible, or copied) instead of compiling again. This is the classic space versus time trade off, but saves an incredible amount of time during a 'make clean; make' run. Andrew Tridgel (Tridge of the Samba project) wrote this version. If gcc were modified to provide this functionality itself, it could do so much more effectively than any external program. Obviously, the feature would be off by default. Thank you for your time. >How-To-Repeat: see http://ccache.samba.org/ for the external program. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-07-08 15:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-08 8:26 danscox [this message] 2002-12-10 17:10 bangerth
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=20020708152158.24720.qmail@sources.redhat.com \ --to=danscox@mindspring.com \ --cc=gcc-gnats@gcc.gnu.org \ /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: linkBe 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).