Difference between revisions of "Design overview"
From MAGEEC
(Listed the three portions of MAGEEC) |
(→Data Gathering) |
||
| Line 4: | Line 4: | ||
==Data Gathering== | ==Data Gathering== | ||
| − | The [[Data_gather| Data gathering]] stage is the initial stage where programs are generated, their features collect and the binary executed on the target platform. The energy data for this is collected and entered into a database | + | The [[Data_gather| Data gathering]] stage is the initial stage where programs are generated, their features collect and the binary executed on the target platform. The energy data for this is collected and entered into a database. |
| + | |||
| + | The interface for this is defined in the [[Data Gather Framework]]. | ||
==Training== | ==Training== | ||
Revision as of 09:15, 4 September 2013
Overall MAGEEC is split into three phases: data gathering, training, and compiler infrastructure.
Data Gathering
The Data gathering stage is the initial stage where programs are generated, their features collect and the binary executed on the target platform. The energy data for this is collected and entered into a database.
The interface for this is defined in the Data Gather Framework.
Training
The training phase takes the data from the database, and learns a classifier.
Compiler Infrastructure
This portion of MAGEEC embeds into the compiler as a plugin, controlling which optimisation passes get executed based on the classifier that was learned previously.
