]>
Commit | Line | Data |
---|---|---|
7a89219d | 1 | --- ccache.1.orig Mon Sep 13 06:38:30 2004 |
2 | +++ ccache.1 Tue Nov 15 14:59:46 2005 | |
3 | @@ -234,6 +234,16 @@ | |
4 | incorrect setting of this debug info rarely causes problems\&. If you | |
5 | strike problems with gdb not using the correct directory then enable | |
6 | this option\&. | |
7 | +.IP | |
8 | +.IP "\fBCCACHE_NOHASH_SIZE_MTIME\fP" | |
9 | +This tells ccache to not hash the real compiler's size and modification | |
10 | +time. Normally this is the mechanism to detect compiler upgrades. | |
11 | +There are situations however, where even though the compiler's size or | |
12 | +modification time has changed you can safely use the cached objects | |
13 | +(e.g. if as part of your build system the compiler is built as well | |
14 | +and the compiler's source has not changed; or if the compiler has only | |
15 | +changes that do not affect code generation). Use this feature only if | |
16 | +you know what you are doing. | |
17 | .IP | |
18 | .IP "\fBCCACHE_UNIFY\fP" | |
19 | If you set the environment variable CCACHE_UNIFY | |
20 | --- ccache.c.orig Mon Sep 13 06:38:30 2004 | |
21 | +++ ccache.c Tue Nov 15 14:59:46 2005 | |
22 | @@ -331,8 +331,10 @@ | |
23 | hash_string(str_basename(args->argv[0])); | |
24 | } | |
25 | ||
26 | - hash_int(st.st_size); | |
27 | - hash_int(st.st_mtime); | |
28 | + if (!getenv("CCACHE_NOHASH_SIZE_MTIME")) { | |
29 | + hash_int(st.st_size); | |
30 | + hash_int(st.st_mtime); | |
31 | + } | |
32 | ||
33 | /* possibly hash the current working directory */ | |
34 | if (getenv("CCACHE_HASHDIR")) { |