Channels ▼
RSS

Optimzing Compiler for Parallelization



Optimizing Technologies has released a beta version of Auto-Parallelizer for Linux on x86, IA64, and PowerPC platforms. Auto-Parallelizer is a tool that looks for parallelizable parts of source code of applications written in a sequential manner and language. In some cases it modifies the source code to maximize the number of such parts or to extend them. For example, users can write a computational program in a sequential manner, then feed the source code to Auto-Parallelizer and the tool will produce code, some parts of which are executable in parallel. This usually speeds up the program execution by several times.

Auto-Parallelizer uses libraries that support OpenMP standard for executing code in parallel. The current implementation uses libgomp, however, it is portable to any existing library that supports all needed interface functions. The implementation currently parallelizes loops only. In the future it will also parallelize sections of sequential code, e.g. several calls.

At present Auto-Parallelizer works only with GCC with the modification the company made in its sorce code. To make it operate you must have:

  • A modified gcc-based compiler that reads and writes program semantics description files
  • Auto-Parallelizer addendum that reads files, analyzes, modifies and writes them back

The modified gcc-based part is available as built for x86 Linux flavors binaries and as a source code. The addendum is isolated from gcc -- it is based on Universal Translating Library. The addendum is available as binary package built for x86 Linux.

The company says it has compared performance results of Auto-Parallelizer beta version with the results icc 11.0.074 (one of the most efficient compiler for x86 and IA64 platforms) and gcc 4.3.1 (one of the most efficient compiler for PowerPC platform. The results of the comparisons are available here:


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.
 

Video