Changeset 379 for anr/section-project-description.tex
- Timestamp:
- Feb 16, 2011, 1:49:14 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-project-description.tex
r364 r379 58 58 This will allow on the one hand to insure that all the tools will 59 59 accept the same C++ description and on the other hand make possible 60 their chaining. The front-end tools read a \xcoach description and generate60 their chaining. The front-end tools read an \xcoach description and generate 61 61 a new \xcoach description that exhibits more parallelism or implement 62 62 specific instructions for ASIP. The back-end tools read an \xcoach … … 64 64 description annotated with hardware information (scheduling, binding) required by 65 65 the VHDL and systemC drivers. 66 Furthermore, the back-end tools use sa macro-cell library (functional and memory66 Furthermore, the back-end tools use a macro-cell library (functional and memory 67 67 unit). 68 68 \parlf … … 153 153 planned at the beginning of the project we will be able to react fast and take 154 154 decisions for possible workaround and enable the continuation of the work with 155 other tasks. Nevertheless, we are confident because upfrontto this project,156 academic partners are already working close tog other and know well each other's155 other tasks. Nevertheless, we are confident becausein preparation to this project, 156 academic partners are already working close together and know well each other's 157 157 technologies, and also a lot of face to face meeting are planned at the 158 158 beginning of the project in task $T2$ in order to define the \xcoach format which is
Note: See TracChangeset
for help on using the changeset viewer.