Hi,

There are no specific locations where you can add support for a new compiler since there is no such compiler abstraction in the code. Instead, the current (relatively small variation in) compiler-specific behavior is handled in a few different places. You can search for config.compiler_type() to find them.

I know next to nothing about the TASKING compiler, but if you want to work on a proof of concept we could certainly have a look at it or give guidance about specific issues.

Hello @vsplesk , were you able to add support for tasking compiler in ccache ? I have tried using the tasking internal cache mechanism (--cache), but the time gain I get is so small that I am evaluating switching to ccache where I would get a better control over the cache search algorithm. Thanks for any advice!

I am sorry, I couldn't find time to work on this project. I have also found --cache option to be not very effective most of the time, i.e. greatly varying between 5% and >> 50% speedup. It's simply not reliable and not as fast as ccache used to be in regular FOSS projects (not sure about our code base, this is yet to be investigated).

In case you start implementing this soon, please send me a note about your fork/branch and I might collaborate there.

There was no demand for the preprocessor mode yet.

I observed ~10% improvement as well on the codebase I used for "--cache"

In case you start implementing this soon, please send me a note about your fork/branch and I might collaborate there.

Same here.

I have started, but I am targeting the tasking tricore compiler (ctc and cctc), is this what you guys are waiting for?

It is for me

I have started the development, I have submitted a first draft for initial merge so that we can start collaborating. #942

@jrosdahl : I have submitted the pull request #942 , it looks like it is waiting for some administrator action. Would you mind having a look and eventually indicating what I need to do to move forward? any advice is welcome!

I tried #942 on a few real-life projects and it worked very smoothly. Build time reduction way over 90% and no inconsistency issues observed so far. Good job!

@louiscaron, tried on the project i'm touching. Good news is that I also saw (unmeasured) 90% improvement.
Unfortunately, there are compilation issues encountered when library files are included with artc component. Perhaps I'm missing something in cmake.

@Joldiges : in my tests, I have only prefixed calls to ctc and cctc with ccache, not artc . still, the error message from ccache is very strange, it probably should not fail even if you prefixed everything with ccache.

I have two questions:

• do you have working elements (ccache prefixing calls to ctc or cctc)?
• can you print the artc full command so I can reproduce your error?

@Joldiges : in my tests, I have only prefixed calls to ctc and cctc with ccache, not artc . still, the error message from ccache is very strange, it probably should not fail even if you prefixed everything with ccache.

I have two questions:

• do you have working elements (ccache prefixing calls to ctc or cctc)?
• can you print the artc full command so I can reproduce your error?

I have identified the problem and it was specific to the CMake command I was using.
The issue was resolved removing RULE_LAUNCH_LINK/RULE_LAUNCH_COMPILE to use CMAKE_C_COMPILER_LAUNCHER.

Just a note on the status of this feature:

• There's a pull request for adding Tricore Tasking support: Support Tricore compiler from Tasking #942.
• My current take on the PR is described in Support Tricore compiler from Tasking #942 (comment) and Support Tricore compiler from Tasking #942 (comment).