Rogue Wave tools support Intel® Xeon Phi™ coprocessors

Rogue Wave Software recently announced expansion of their support of Intel Xeon Phi coprocessors which will now includes their SourcePro* C++, IMSL* Numerical Libraries, TotalView* debugger, and the ThreadSpotter* cache memory optimizer products.  You can check out their press release for details.

Scott Lasica, VP Products and Alliances at Rogue Wave Software, helped me understand this value by sharing with me: "When we started porting TotalView to run on a Xeon Phi coprocessor, we progressed in a week what took us over a year with an accelerator." The common x86 programming model, Linux-based environment and suite of Intel Tools allowed them to support Intel Xeon Phi coprocessor in a few weeks instead of many months without the Intel Xeon Phi coprocessor advantages.

I'm pleased to have Rogue Wave offering solutions for our customers for Intel Xeon Phi coprocessor development. Many of our customers have expressed to me personally how happy they are to have Rogue Wave tools supporting Intel Xeon Phi coprocessors.

As with other tools, a key benefit is that these are NOT new tools or wildly different add-ons to their tools. Instead, they are familiar tools with familar features. They are similar by simply extending their x86 support to include the "many" core aspects of Intel Xeon Phi coprocessors including "the over 50 cores" and the "512 bit wide SIMD."  This is very similar to supporting a 50+ core processor shared memory machine.  That's why application developers and tool developers are finding it straight forward to work with Intel Xeon Phi coprocessors.  I call this a dual-tuning/optimization benefit of Intel Xeon Phi coprocessors - the ability of programming languages, model and tools to benefit both processors and Intel Xeon Phi coprocessors. That preserves past investments in coding and training, as well as investment today in both. That's an advantage that makes the tough job of programming just a little easier.


For more complete information about compiler optimizations, see our Optimization Notice.