arrow_back_ios Back to List

How does Sieve integrate with my current tool chain?

The sieve toolkit easily integrates with existing standard C/C++ development tools that you may already be using, this includes an existing C/C++ compiler (such as GCC) which may be the only compiler supporting your new processor architecture.

Here is an illustration of how the Sieve System components provided by Codeplay integrate into existing development tool chains:

Untitled 1. Development begins with the C++ Source Code. Using your existing IDE and version control system, combined with the Sieve programming tools, you can modify your existing code base or write entirely new programs marked up with Sieve.

2. The Target Descriptor file allows programmers to enable and configure specific processor features in the Sieve compiler.

3. Applying Sieve is minimally invasive to your code and requires no changes to data structures so it is easy to use #defines to enable and disable Sieve extensions.

4. The Sieve compiler compiles your Sieve C++ code into an ANSI C form, similar to bytecode, using Codeplay s OutputC technology. The C code has been parallelized to the specifications of the target multi-core architecture and is ready to be compiled into objects using your existing C/C++ compiler.

5. The Sieve Runtime library provides processor specific implementations of Sieve. This is the only architecture dependent component, and Codeplay can provide or build a runtime for any existing or future multi-core processor.

This ensures that Sieve code is portable. Programs do not have to be rewritten or extensively modified to run on radically different multi-core processor designs.

6. The object files and the Sieve runtime library can then be linked using your existing linker.

7. Finally we have our software application, ready to take full of advantage of the processing power of the target multi-core device.