I have confirmed that a few files can be different due to our generation code.
There are no volatile pieces such as preprocessor macros and such, just good
non-deterministic print orders in our generation code. I believe this should
be the culprit but unfortunately will take a bit for me to cl
On 25/06/2019 00:28, Malfettone, Kris via ccache wrote:
> So what I seem to be observing is only when I do a ninja -t clean or make
> clean. This removes all of my generated files (.h and .cpp files) and of
> course the normal build outputs. A subsequent run is then mostly cache
> misses. If
On Tue, 25 Jun 2019 at 00:28, Malfettone, Kris via ccache
wrote:
> So what I seem to be observing is only when I do a ninja -t clean or make
> clean. This removes all of my generated files (.h and .cpp files) and of
> course the normal build outputs. A subsequent run is then mostly cache
> misses.
