Reporting Issues with TBB

What should I do when I find a TBB bug?

First, please check Intel® TBB FAQ and  Intel® TBB Forum to see if this issue is being discussed there before you submit it.  Then use the Intel® TBB Forum to submit your issue.

What information should I provide when filing a new bug report?

Choose a title that uniquely and concisely describes your bug. Enter a specific description of your bug; describe your system configuration -- include platform, architecture, operating system, ABI and compiler information, along with specific versions used -- and the details necessary to reproduce your bug. Include as small a test-case as is adequate to reproduce the bug, along with the specific commands used to compile and run the test-case. Include any additional, specific details that may be relevant. Indicate the release type, file name and version of the most recent TBB Download that reproduces the bug; please indicate whether release or debug library builds were used. Indicate the severity of the bug in terms of its impact to you and your productivity:

  • Showstopper - A bug that prevents you from using TBB.
  • High - A bug with a short-term workaround, but which needs to be fixed as soon as possible.
  • Medium - A bug that does not slow development, but which needs to be fixed.
  • Low - A bug that has no significant impact, but which should be fixed at some point to improve future usability.
What should I do if I have a question about Intel® TBB?

Please check the Intel® TBB FAQs; if you cannot find the answer there, please raise the issue on the Intel® TBB discussion forum.

Does Intel plan to make its TBB quality test suites available?

Yes we will. With the source code, we include unit tests. The unit tests accomplish basic performance testing of the various small constructs in TBB. There are also examples that time themselves for doing basic performance measurements. This is an area that we think can use additional attention.