| |
 |
 |
|
|
 |
 |
 |
Gedae Solution |

|
The Gedae compiler handles the complexity. Since the Gedae compiler is aware of the multi-processor and the multi-core and memory architecture of the target, it automatically customizes the software to that architecture. As a result, it’s easy to port applications among processors. The Gedae language provides the compiler with information in a form that allows the compiler to automatically perform the most complex tasks, including threading the application, planning memory and implementing the distribution of the software. |
 |
|
Middleware Solution |

|
Middleware attempts to simplify software development by providing a platform-independent method of specifying common operations. The architecture-specific code is separated from the algorithmic IP using a layer of software. There is a tradeoff in the development of this software layer between efficiency and making it general purpose. A general purpose library must be able to handle many contingencies, and these contingencies lead to slower execution and larger code lying underneath the software layer. In this sense, middleware contains complexity; it only solves a small number of problems and in doing so requires a rigid and overly complex interface. |
 |
|
Traditional Solution |

|
In a traditional development process systems engineering provides the specification of the system and software, and the development team is responsible for all of the complexity of the system. The compiler has no knowledge or awareness of the multi-processor nature of the target processor, so multiple threads of execution are required. The development team has to be aware of and accommodate the target architecture |
 |
|
|
|
| |
|
|
|
 |
|
 |
Copyright © Gedae, 2009-2011. |
Try/Buy |
 |
|
|
|