[petsc-dev] ccache tips?

Patrick Sanan patrick.sanan at gmail.com
Mon Jan 20 08:36:44 CST 2020

Thanks a lot for all the tips! I'm trying things out now with an approach like Jed's, but attempting to use system MPI instead of a specific build of MPICH.

> Am 17.01.2020 um 22:13 schrieb Jed Brown <jed at jedbrown.org>:
> "Balay, Satish" <balay at mcs.anl.gov> writes:
>> I guess you can just create links [from mpicc to ccache] instead of
>> these wrapper scripts in these locations - with the same ccache
>> performance?
> I don't because I have multiple mpicc at different paths.
>> And with the scripts [mpicc/mpicxx links to ccache] in PATH - you
>> don't need --with-mpi-dir [and mpiexec/include/lib work-around]
> Sure, but then it's global (all calls to gcc or clang are processed via
> ccache).  Probably harmless, but may needlessly flush your cache.
>> Also is there an advantage to have mpicc linked to ccache instead of
>> gcc? [I guess having both linked to ccache will result in duplicate
>> ccache searches for the same command?]
> I want the precision of gcc with/without ccache and (OMPI or MPICH)
> mpicc with/without ccache.  Other solutions are good if you just want
> ccache all the time.

More information about the petsc-dev mailing list