# Cell software development > Mediated Wiki article. Canonical URL: https://mediated.wiki/source/Cell_software_development > Markdown URL: https://mediated.wiki/source/Cell_software_development.md > Source: https://en.wikipedia.org/wiki/Cell_software_development > Source revision: 1340601521 > License: Creative Commons Attribution-ShareAlike 4.0 International (https://creativecommons.org/licenses/by-sa/4.0/) '''Software development''' for the [Cell microprocessor](/source/Cell_microprocessor) involves a mixture of conventional development practices for the [PowerPC](/source/PowerPC)-compatible PPU core, and novel software development challenges with regard to the functionally reduced SPU coprocessors. ==Linux on Cell== An open source software-based strategy was adopted to accelerate the development of a Cell BE ecosystem and to provide an environment to develop Cell applications, including a GCC-based Cell compiler, binutils and a port of the Linux operating system.{{cite web|url=http://www.research.ibm.com/people/m/mikeg/papers/2007_ieeecomputer.pdf|title=An Open Source Environment for Cell Broadband Engine System Software|date=June 2007}} ==Octopiler== '''Octopiler''' is [IBM](/source/IBM)'s prototype [compiler](/source/compiler) to allow [software developer](/source/software_developer)s to write [code](/source/software_code) for [Cell processor](/source/Cell_processor)s.{{citation|title=Using advanced compiler technology to exploit the performance of the Cell Broadband Engine architecture|date=2017-10-23|url=http://www.research.ibm.com/journal/sj/451/eichenberger.html|archive-url=https://web.archive.org/web/20060411094457/http://www.research.ibm.com/journal/sj/451/eichenberger.html|archive-date=2006-04-11|url-status=dead|publisher=IBM Systems Journal}}{{Cite web|date=2006-01-20|title=Compiler Technology for Scalable Architectures|url=https://www.empat.tech/services|archive-url=https://web.archive.org/web/20080320071448/http://domino.research.ibm.com/comm/research_projects.nsf/pages/cellcompiler.index.html|archive-date=2008-03-20|access-date=2025-06-11|website=IBM Research|language=en-us}}{{Cite web|last=Stokes|first=Jon|date=2006-02-26|title=IBM's Octopiler, or, why the PS3 is running late|url=https://arstechnica.com/uncategorized/2006/02/6265-2/|access-date=2025-06-11|website=Ars Technica}} ==Software portability== ===Adapting VMX for SPU=== ====Differences between VMX and SPU==== The [VMX](/source/AltiVec) (Vector Multimedia Extensions) technology is conceptually similar to the vector model provided by the SPU processors, but there are a number of significant differences. {| class="wikitable" style="margin: 1em auto 1em auto" |+ '''VMX to SPU Comparison'''{{ref|vmxrefman}}
''unfinished'' ! feature || VMX || SPU |- ! [word](/source/Word_(data_type)) size | 32 bits || 32 bits |- ! number of [registers](/source/Processor_register) | 32 || 128 |- ! register width | 128-bit quadword || 128-bit quadword |- ! [integer](/source/integer) formats | 8, 16, 32 || 8, 16, 32, 64 |- ! saturation support | yes || no |- ! byte ordering | big (default), little || big endian |- ! [floating point](/source/Floating-point_arithmetic) modes | Java, non-Java || single precision, IEEE double |- ! [Memory alignment](/source/Data_structure_alignment) | quadword only || quadword only |} The VMX ''[Java](/source/Java_(programming_language)) mode'' conforms to the [Java Language Specification](/source/Java_Language_Specification) 1 subset of the default [IEEE Standard](/source/IEEE_Standard), extended to include IEEE and [C9X](/source/C99) compliance where the Java standard falls silent. In a typical implementation, non-Java mode converts [denormal](/source/denormal) values to zero but Java mode traps into an emulator when the processor encounters such a value. The IBM PPE Vector/SIMD manual does not define operations for double-precision floating point, though IBM has published material implying certain double-precision performance numbers associated with the Cell PPE VMX technology. ====Intrinsics==== Compilers for Cell{{Who|date=February 2011}} provide [intrinsic](/source/intrinsic_function)s to expose useful SPU instructions in C and C++. Instructions that differ only in the type of operand (such as a, ai, ah, ahi, fa, and dfa for addition) are typically represented by a single C/C++ intrinsic which selects the proper instruction based on the type of the operand. ====Porting VMX code for SPU==== A substantial amount of VMX ([Altivec](/source/Altivec)) code developed for [IBM Power microprocessors](/source/IBM_Power_microprocessors), particularly under the [PowerPC](/source/PowerPC) version of [macOS](/source/macOS), can potentially be adapted for use on the SPU. The feasibility of porting depends on the extent of VMX-specific features used—ranging from straightforward to impractical. However, key workloads typically map well to the SPU architecture. In some cases, existing VMX code can be ported directly. If the VMX code is highly generic (makes few assumptions about the execution environment) the translation can be relatively straightforward. The two processors specify a different [binary code format](/source/binary_format), so recompilation is required at a minimum. Even where [instructions](/source/Instruction_(computer_science)) exist with the same behaviors, they do not have the same instruction names, so this must be mapped as well. IBM's development toolkit includes compiler intrinsics that automate much of this mapping. In multiple cases, however, a directly equivalent instruction does not exist. The workaround might be obvious or it might not. For example, if saturation behavior is required on the SPU, it can be coded by adding additional SPU instructions to accomplish this (with some loss of efficiency). At the other extreme, if Java floating-point semantics are required, this is almost impossible to achieve on the SPU processor. To achieve the same computation on the SPU might require that an entirely different [algorithm](/source/algorithm) be written from scratch. The most important conceptual similarity between VMX and the SPU architecture is supporting the same [vectorization model](/source/vectorization_model). For this reason, most algorithms adapted to Altivec will usually adapt successfully to the SPU architecture as well. ==Local store exploitation== Transferring data between the local stores of different SPUs can have a large performance cost. The local stores of individual SPUs can be exploited using a variety of strategies. Applications with high locality, such as dense matrix computations, represent an ideal workload class for the local stores in Cell BE.{{cite web|url=http://www.research.ibm.com/people/m/mikeg/papers/2006_ieeemicro.pdf|title=Synergistic Processing in Cell's Multicore Architecture|date=March 2006}} Streaming computations can be efficiently accommodated using [software pipelining](/source/software_pipelining) of memory block transfers using a multi-buffering strategy. The software cache offers a solution for random accesses.{{cite web|url=http://www.research.ibm.com/journal/sj/451/eichenberger.pdf|title=Using advanced compiler technology to exploit the performance of the Cell Broadband Engine architecture|date=January 2006}} More sophisticated applications can use multiple strategies for different data types.{{cite web|url=http://www.research.ibm.com/cell/papers/2008_vee_cellgc.pdf|title=Cell GC: Using the Cell Synergistic Processor as a Garbage Collection Coprocessor |date=March 2008}} ==References== * [http://www.research.ibm.com/cell/ The Cell Project at IBM Research] * [http://cag.csail.mit.edu/crg/papers/eichenberger05cell.pdf Optimizing Compiler for a CELL Processor] * [https://dx.doi.org/10.1147/sj.451.0059 Using advanced compiler technology to exploit the performance of the Cell Broadband Engine architecture] * [http://domino.research.ibm.com/comm/research_projects.nsf/pages/cellcompiler.index.html Compiler Technology for Scalable Architectures] {{Webarchive|url=https://web.archive.org/web/20090129204113/http://domino.research.ibm.com/comm/research_projects.nsf/pages/cellcompiler.index.html |date=2009-01-29 }} {{reflist}} {{Cell microprocessor segments}} {{DEFAULTSORT:Cell Software Development}} Category:Cell BE architecture Category:Compilers Category:Vaporware --- Adapted from the Wikipedia article [Cell software development](https://en.wikipedia.org/wiki/Cell_software_development) by Wikipedia contributors ([contributor history](https://en.wikipedia.org/wiki/Cell_software_development?action=history)). Available under [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/). Changes may have been made.