I was able to create test case that reproduces this, and I've submitted a problem report to the driver development team here. I don't have any good workarounds at this point other than doing the archiving in a separate step that you do with -j1.
I'm going to move this thread (maintaining a pointer here) to the Intel C++ Compiler forum since this is really a compiler issue and not a Cilk Plus issue.
Hi create simple Makefile where could be used make --jobs=(2 or more) i think not judicious to use two sides shared simultaneous build ipo side have use already is internal simultaneous process. Large program give catastrophic consumption with this way. result is only the time build could be increased. Sometime swap disk full run infinite in round. but maybe, you have probably an reason that justify it required. Regards
If I understand correctly, Bustaf was referring to the parallel facilitiy in Gnu Make, which is independent of the compiler you're using. In other words, it's not icc that's using multiple processes but make, though each of those processes may be running icc. I've used make -j N for values of N from 2 to 16 with success. If you're using Make for your build and you have 10 cores available, you could try adding -j 10 (or maybe even 15 or 20), but as Bustaf points out it may take a lot of memory. If your project is big or some individual files are big, then the available memory may be your limiting factor.