Channels ▼


HMPP Pushed As a New Open Standard

PathScale, a provider of high performance AMD64 and Intel64 compilers, has announced its new PathScale ENZO Compiler Suite will support NVIDIA GPUs using the HMPP directive-based programming model originally developed by CAPS. CAPS and PathScale have also jointly started working on advancing the HMPP directives as a new open standard. The new ENZO Compiler Suite is available for testing by selected customers and will be generally available later this summer.

“Our new ENZO compilers not only bring performance to another level by exploiting the NVIDIA GPU's, but also allow incremental changes without sacrificing maximum performance” according to Christopher Bergstrom, Chief Technical Officer at PathScale. “By jointly working together with CAPS on making HMPP directives an open standard, we make possible a new evolution in the General-Purpose computation on Graphics Processing Units (GPGPU) programming model that has been long overdue.”

The HMPP directives have been designed and used for more than 2 years by major HPC leaders. As a high level of abstraction for programming GPUs in scientific applications, HMPP preserves customer software assets by keeping applications portable. The HMPP directive-based programming model offers a powerful syntax to efficiently offload computations on hardware accelerators and to optimize data movement.

“PathScale’s choice to implement the HMPP directive programming model in their ENZO compiler suite supports CAPS commitment in delivering to users an open standard solution that will secure their investment”, said Francois Bodin, Chief Technical Officer at CAPS.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.