Backend Signals error when compiling code including Intel® Cilk™ Plus headers

Reference Number : DPD200159529

Version : 2011

Product : Intel® Parallel Composer

Operating System : Windows*

Problem Description : When compiling multiple files in a Visual C++ project with the Intel® C++ Compiler or compiling multiple files on one command line, you may see a backend signals internal error if the files are using Intel® Cilk™ Plus header files.  You can confirm this issue applies to you if you can compile any one source file without seeing the backend signals error.

Resolution Status : Our developers are working towards a fix for this issue.  If a workaround is needed, please contact us via User Forum or Intel® Premier Support.  This issue does not exist in the Intel® C++ Composer XE.

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
For more complete information about compiler optimizations, see our Optimization Notice.