Re: [ccache] ccacje direct mode without fall back to running the preprocessor

On 10 December 2015 at 20:32, vkr wrote: > Sorry. It is not the manifest file that it tries to update. But the ".d" > files. I think it is a real bug. [...] > Yes, good catch. Thanks! Fixed like suggested in a7ab503f07e31ebeaaec34fbaa30e264308a299d

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

On 10/12/15 19:32, vkr wrote: Sorry. It is not the manifest file that it tries to update. But the ".d" files. I think it is a real bug. In read-only mode, when ccache tries to run cache look up in preprocessor mode, it tries to put_file_in_cache for .d file unconditionally. if (generat

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

Sorry. It is not the manifest file that it tries to update. But the ".d" files. I think it is a real bug. In read-only mode, when ccache tries to run cache look up in preprocessor mode, it tries to put_file_in_cache for .d file unconditionally. if (generating_dependencies && mode == FROMC

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

Andrew Stubbs wrote: > You really are getting into shaving fractions now though. At this point > you should seriously consider linking ccache statically; run it with > callgrind and you can see that a significant proportion of time is spent > before "main" is even called, loading libraries and such

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

On 10/12/15 03:13, vkr wrote: Hello Andew, The answer is "no", because it is necessary to run the preprocessor in order to fill the cache and record the file list that direct mode lookups use. What are the consequences if we don't let ccache record the file list, but just run the preprocessor

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

Hello Andew, > The answer is "no", because it is necessary to run the preprocessor in order to fill the cache and record the file list that direct mode lookups use. What are the consequences if we don't let ccache record the file list, but just run the preprocessor and do a cache lookup using the

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

Hello. Sure, that name is an apt one and I'm glad saved a few seconds :) Regards, venkrao On Tue, Sep 16, 2014 at 12:54 AM, Joel Rosdahl wrote: > Hi, > > I'm not opposed to introducing such an option. What would be a good name? > CCACHE_READONLY_DIRECT (readonly_direct in the config file on mas

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

Hi, I'm not opposed to introducing such an option. What would be a good name? CCACHE_READONLY_DIRECT (readonly_direct in the config file on master)? -- Joel On 10 September 2014 09:57, Andrew Stubbs wrote: > On 10/09/14 08:24, vkr wrote: > >> Why is that? I mean, when drop preprocessing only

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

On 10/09/14 08:24, vkr wrote: Why is that? I mean, when drop preprocessing only when an env variable is set, why is it not the right approach? The development sources on the master branch has all-new option and environment variable processing code. The part where you act on the option is pro

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

Hi Andrew, > It's not the right implementation for the master branch, but might be ok in > the release branch? Why is that? I mean, when drop preprocessing only when an env variable is set, why is it not the right approach? Regards, Venkrao On Mon, Sep 8, 2014 at 4:32 PM, Andrew Stubbs wrote: >

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

On 08/09/14 11:37, vkr wrote: If the env variable TRS_CCACHE_NO_PREPROCESSOR_ON_DIRECT_LOOKUP_MISS is set then, I do not run preprocessing, but just fall back to running real-compiler. I see a lot of time saving, and I can't think of any side-effect. It's not the right implementation for the m

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

On 08/09/14 11:37, vkr wrote: If the env variable TRS_CCACHE_NO_PREPROCESSOR_ON_DIRECT_LOOKUP_MISS is set then, I do not run preprocessing, but just fall back to running real-compiler. I see a lot of time saving, and I can't think of any side-effect. It's not the right implementation for the m

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

Hi Andrew It seems to me that I can switch off preprocessing in a read-only ccache mode, after a direct lookup fail. How do you see the following patch? If the env variable TRS_CCACHE_NO_PREPROCESSOR_ON_DIRECT_LOOKUP_MISS is set then, I do not run preprocessing, but just fall back to running real-

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

Hello First of all, sorry about the typo in the subject/title of my post. I run ccache in read-only mode itself. But, I still see that after the direct cache lookup fail, it falls back to running the preprocessor. That's exactly what I wanted to avoid. It seems to me that having an option to avoi

Re: [ccache] ccacje direct mode without fall back to running the preprocessor

On 04/09/14 08:32, vkr wrote:> I would like to know if I can avoid > "If there is no match, ccache falls back to running the preprocessor." The answer is "no", because it is necessary to run the preprocessor in order to fill the cache and record the file list that direct mode lookups use. It