| 1 |
On Thu, 02 Feb 2006 15:35:33 -0500 |
| 2 |
Ned Ludd <solar@g.o> wrote: |
| 3 |
|
| 4 |
> On Thu, 2006-02-02 at 20:35 +0100, Kevin F. Quinn (Gentoo) wrote: |
| 5 |
> > On Thu, 02 Feb 2006 13:18:46 -0500 |
| 6 |
> > Ned Ludd <solar@g.o> wrote: |
| 7 |
> > |
| 8 |
> > > On Thu, 2006-02-02 at 17:59 +0000, Ed W wrote: |
| 9 |
> > > > Heads up then that when switching compiler to the non-hardened |
| 10 |
> > > > one it makes sense to blow away the ccache of disable it's use. |
| 11 |
> > > |
| 12 |
> > > That probably makes sense for any time a gcc-config switch |
| 13 |
> > > happens. You should probably file a bug about that for the |
| 14 |
> > > maintainer of gcc-config. |
| 15 |
> > |
| 16 |
> > ccache doesn't take account of anything other than the built-in |
| 17 |
> > specs files and stuff specified via --specs - we could just patch |
| 18 |
> > ccache to pay attention to GCC_SPECS as well. I'll take a look. |
| 19 |
> |
| 20 |
> Ok cool but keep in mind. |
| 21 |
> |
| 22 |
> USE=-hardened emerge gcc |
| 23 |
> gcc-config 1 |
| 24 |
> echo $GCC_SPECS |
| 25 |
> |
| 26 |
> USE=hardened emerge gcc |
| 27 |
> gcc-config 1 |
| 28 |
> echo $GCC_SPECS |
| 29 |
> |
| 30 |
> Both times it shall be "" with the same version of gcc. |
| 31 |
|
| 32 |
The hash does include the size & mtime of the compiler driver - |
| 33 |
although that'll be the wrapper in most cases, I guess, which may not |
| 34 |
be good enough. |
| 35 |
|
| 36 |
bug #121336 btw |
| 37 |
|
| 38 |
actually I think hashing the files in GCC_SPECS won't work, as ccache |
| 39 |
doesn't see GCC_SPECS because it's set by the compiler wrapper. |
| 40 |
|
| 41 |
I think it may be enough to hash in the output of '<compiler> -v'... |
| 42 |
-- |
| 43 |
Kevin F. Quinn |
Archives