Skip to Content
Last modified by Alexander Schulz-Rosengarten on 2023/09/11 16:17
From version 13.1
edited by cmot
on 2014/02/10 20:55
Change comment: There is no comment for this version
To version 18.1
edited by cmot
on 2014/02/10 21:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -100,8 +100,60 @@
100 100  
101 101  [[image:attach:kieler12.png]]
102 102  
103 -
103 +You will now see how to generate a C tick function.
104 104  
105 105  = Generate C Code =
106 106  
107 -xxx
107 +You can do several transformations on SCCharts (*.sct files). Just right click the file you want to transform in the project explorer and select the Transform SCChart sub menu. As abo is already a Core SCCart you do not need the core transformations. Click the All Normalize Transformations, this will do the Split Trigger and Effects and the Surface and Depth transformations together (in this order).
108 +
109 +[[image:attach:kieler13.png]]
110 +
111 +After performing a transformation the transformed SCChart will open (together with it's KLighD diagram visualization):
112 +
113 +[[image:attach:kieler14.png]]
114 +
115 +Now generate the Sequentially Constructive Graph (SCG) from the normalized form. You do this also in the context menu of the Project Explorer by selecting the *.normalized.sct and choosing Generate SCG. When selecting the abo.normalized.scg file the SCG diagram will be automatically synthesized (you may also want to re-arrange the KLigD view by dragging in to the right side again).
116 +
117 +[[image:attach:kieler15.png]][[image:attach:kieler16.png]]
118 +
119 +
120 +
121 +You can now populate the SCG automatically with dependency data. Choose Transform SCG -> SCG with Dependency Data from the context menu (left side). This will result in the following SCG (right side).
122 +
123 +[[image:attach:kieler17.png]][[image:attach:kieler18.png]]
124 +
125 +
126 +
127 +Now populate the SCG with basic block information (left side). The SCG with calculated basic blocks will look like this (right side).
128 +
129 +[[image:attach:kieler19.png]][[image:attach:kieler20.png]]
130 +
131 +
132 +
133 +The next step in compilation is the (more fine grained) calculate of scheduling blocks (left side). The populated SCG with scheduling information looks like this (right side).
134 +
135 +[[image:attach:kieler21.png]][[image:attach:kieler22.png]]
136 +
137 +
138 +
139 +The SCG is now ready to be sequentialized. A primitive scheduler currently is included in KIELER but more elaborate ones are already in the pipe line (left side). The sequentialized SCG looks like this (right side).
140 +
141 +[[image:attach:kieler23.png]][[image:attach:kieler24.png]]
142 +
143 +
144 +
145 +From here its only a short hop to C code. Transform the sequentialized SCG into an S Tick Function (left side). When opening the S file (abo.normalized.seq.s) this already is very c like code (right side).
146 +
147 +[[image:attach:kieler25.png]][[image:attach:kieler26.png]]
148 +
149 +
150 +
151 +Selecting Generate SC will produce a C file:
152 +
153 +[[image:attach:kieler27.png]][[image:attach:kieler28.png]]
154 +
155 +
156 +
157 +
158 +
159 +
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -8651723
1 +8651733
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651723/PLDI'14 Artifact on SCCharts
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651733/PLDI'14 Artifact on SCCharts