The Gecos (Generic Compiler Suite) project is an open source compiler infrastructure developed in the CAIRN group since 2004. Gecos was initially designed so as to address part of the shortcomings of existing C/C++ infrastructures such as SUIF. Its main characteristics are high-lighted below:
Gecos is an open source software and is hosted on Inria GForge.
For users unfamiliar with Eclipse, we currently provide three versions of a bundle Eclipse distribution including gecos, CDT and Xtext. If you don't want to mess with Eclipse update sites, this is definitely the way to go.
Important : In order to get the latest GeCoS version, please check for updates after installing the Eclipse bundle (“Help” → “Check for Updates”).
Please follow this link to get more information about the installation procedure
Here, you can find what are the new features in gecos and which bugs are fixed.
In this section we will provide a set of tutorials, targeting beginners as well as advanced users. It's mainly divided into 2 sections:
NOTE: As gecos is a rapidly changing software, some tutorials may not be up-to-dated or contain bugs. If you encounter any problem please report it either on the gecos-user mailing lists or report a bug on the bug tracking page
All the GeCoS Tutorials are available in this pdf file
Below, we provide an introduction to Lomita :
Below, we provide a short description of most of functions available in gecos script :
Some documentation to help in managing SVN :
#pragma omp for parallel
error while evaluating 'script.cs':
whenever I try to run a .cs file.run gecos script
command in the context menu when I want to run a Gecos script. Here is the link to go to the section reserved to Gecos contributor.
In that case please report the problems that you encoutered either on the gecos-user mailing lists or report a bug on the bug tracking page
There are several mailing lists, wich can be found here
To help us being more repsonvise w.r.t to bugs, we have set up a detailed bug submission procedure, and need you to strictly follow these guidelines :
Then, if you are just a Gecos user, go on the Gecos bug tracking page and start by providing a precise and detailled description of the problem that you encoutered. Whenever possible, please attach the script file (.cs
) and a simple source code example that will help us reproduce the bug.
Otherwise if you are a registered Gecos developpers (i.e. with write access to the SVN), you need to commit the script file and source file to the fr.irisa.cairn.gecos.bugs
in the following SVN folder https://scm.gforge.inria.fr/svn/gecos/trunk/test/fr.irisa.cairn.gecos.bugs
, using the following convention.
bug-123
)