Intel® IPP 8.2 Update 2 packages are now ready for download. Intel® IPP is available as part of Intel® Parallel Studio XE, Intel® System Studio, Intel® Integrated Native Developer Experience (Intel® INDE), Intel® Integrated Native Developer Experience 2015 Build Edition for OS X*
As part of the application readiness efforts for future Intel® Xeon® processors and Intel® Xeon Phi™ coprocessors (code named Knights Landing), developers are interested in improving two key aspects of their workloads:
- Vectorization/code generation
- Thread parallelism
This article mainly talks about vectorization/code generation and lists some helpful tools and resources for thread parallelism.
Intel MKL Users,
We would like to Introduce a new feature Intel® MKL Cookbook, an online Document with recipes for assembling Intel MKL routines for solving complex problems.Please give us your valuable feedback on these Cookbook recipes, and let us know if you want us to include more recipes and/or improve existing recipes.
Thank you for Evaluating
Intel MKL Team
Intel MKL users,
We would like to hear from you how you are using Intel MKL with threading. Do you use the parallel or sequential MKL? How do your multithreaded applications use MKL? We would appreciate you to complete a short survey. It takes no more than 5 minutes. Your feedback will help us to make Intel MKL a better product. Thanks!
Survey link: https://idz.qualtrics.com/SE/?SID=SV_5Bmh232m96WJK3b
The attached document describes some common issues and questions that have been reported and how they might be addressed.
Are you having problems with your hardware (Cannot see your Intel(R) Xeon Phi(tm) coprocessor? Sporadic accessibility?) or with the Intel(R) Manycore Platform Software Stack (Intel(R) MPSS) running reliably?
Attached to this post are PDF "flowcharts" that explain how you can troubleshoot the problem (note: Both Linux and Windows flowcharts are available), and shows what information you will want to collect if you need to escalate your issue to your OEM provider or Intel.
Do you have questions that you are not finding the answers for in our documentation? Need more training, source code examples, on what specifically? Help us understand what's missing so that we can make sure we develop documentation you care about (what is important, and what is nice to have)! Thank you