Changes for page Kieler Compiler
Last modified by Richard Kreissig on 2023/09/14 10:52
From version 29.1
edited by Alexander Schulz-Rosengarten
on 2018/11/22 14:54
on 2018/11/22 14:54
Change comment:
There is no comment for this version
To version 6.1
edited by cmot
on 2014/03/16 22:21
on 2014/03/16 22:21
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Kieler Compiler 1 +Kieler Compiler (KiCo) - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. als1 +XWiki.cmot - Content
-
... ... @@ -1,22 +17,6 @@ 1 -{{panel bgColor="orange" title="Deprecated since 0.12"}} 2 -This article is deprecated. The described features are no longer available in current releases. 3 -{{/panel}} 4 - 5 -{{panel borderStyle="dashed" title="Project Overview"}} 6 -Responsible: 7 - 8 -* [[Christian Motika>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/cmot/||shape="rect"]], [[Steven Smyth>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/ssm/||shape="rect"]] 9 - 10 -Related Theses: 11 - 12 -* none yet 13 - 14 -**To see the KielerCompiler in action, we provide an Online SCCharts Compiler [[here>>doc:Online Compiler]].** 15 -{{/panel}} 16 - 17 17 = Kieler Compiler (KiCo) = 18 18 19 -In order to integrate and be able to evaluate our compiler chain from SCCharts to C or VHDL code we use the KiCo project as a generic framework that allows to register setp-by-step transformations on EObjects. These can then be handled by the generic KIEM KiCo DataComponent. **To see the KielerCompiler in action, we provide an Online SCCharts Compiler [[here>>url:http://www.sccharts.com/||shape="rect"]].**3 +In order to integrate and be able to evaluate our compiler chain from SCCharts to C or VHDL code we use the KiCo project as a generic framework that allows to register setp-by-step transformations on EObjects. These can then be handled by the generic KIEM KiCo DataComponent. 20 20 21 21 22 22 ... ... @@ -26,18 +26,7 @@ 26 26 27 27 The KIELER Compiler (KiCo) project allows to register step-by-step model transformations on EObjects that could be written in Xtend or Java. These transformations are registered using an extension point provided (see below). After registering transformations these can be used by simply call the KielerCompiler compilation method as also explained further below. 28 28 29 -(% class="wrapped" %) 30 -|=((( 31 -(% class="content-wrapper" %) 32 -((( 33 -[[image:attach:IMAG4642.jpg]] 34 -))) 35 -)))|=((( 36 -(% class="content-wrapper" %) 37 -((( 38 38 [[image:attach:KiCo.jpg]] 39 -))) 40 -))) 41 41 42 42 == Extension Point == 43 43 ... ... @@ -48,21 +48,17 @@ 48 48 49 49 {{{de.cau.cs.kieler.kico}}} 50 50 51 - \\24 + 52 52 ))) 53 53 1. Add the extension 54 54 55 55 56 -{{{de.cau.cs.kieler.kico.transformation}}}((( 57 -\\ 58 -))) 59 -1. ((( 60 -Add one of the following extension element 29 +{{{de.cau.cs.kieler.kico.transformation}}} 61 61 31 +Add one of the following 32 + 62 62 [[image:attach:KiCo2.jpg]] 63 -))) 64 64 65 -(% class="wrapped" %) 66 66 |=((( 67 67 Extension Element 68 68 )))|=((( ... ... @@ -87,7 +87,7 @@ 87 87 * method: The name of the transformation method. Its signature must ensure that it returns an EObject an only take an EObject argument. Otherwise it cannot be found by KiCo. 88 88 * id: The unique String ID for this transformation. This is the ID the transformation will be referenced throughout KiCo. 89 89 * name: An optional String name for this transformation. If nothing is entered here the ID will be used as a name. 90 -* dependencies: An optional String as comma separated list of other transformation IDs that must run AFTER this transformationdown the compile-chain.This means if the current transformation is selected to run, all transformations that have dependencies on this will be run BEFORE.If nothing is entered here then this means there are no dependencies.59 +* dependencies: An optional String as comma separated list of other transformation IDs that must run BEFORE this transformation. If nothing is entered here then this means there are no dependencies. 91 91 ))) 92 92 |((( 93 93 transformationGroup ... ... @@ -95,9 +95,8 @@ 95 95 Sometimes you may want to group other transformations and give this group a specific transformation ID as a kind of shortcut. You can do this by using the transformationGroup element giving the following information: 96 96 97 97 * id: The unique String ID for this transformation group. This is the ID the transformation group will be referenced throughout KiCo. It may also again be referenced by other transformation groups! 98 -* transformations:Groups must specify their transformations. Use a String as comma separated list of other transformation IDs or transformation group IDs that should represent this group. Note that the order will be implied by the referenced transformations itself although if there is a free degree of order it can be influenced by the order specified here in the group.67 +* dependencies: These are NOT optional for groups. Groups must specify their transformations as dependencies. Use a String as comma separated list of other transformation IDs or transformation group IDs that should represent this group. Note that the order will be implied by the referenced transformations itself although if there is a free degree of order it can be influenced by the order specified here in the group. 99 99 * name: An optional String name for this transformation. If nothing is entered here the ID will be used as a name. 100 -* alternatives: When selected this group specifies alternatives only. When this group is referenced, the first transformation is selected if not any other transformation from this group is already in the list of selected transformations. This is an advanced feature. 101 101 ))) 102 102 103 103 === Example === ... ... @@ -110,7 +110,9 @@ 110 110 dependencies="TRIGGEREFFECT, SURFACEDEPTH" 111 111 name="Transform All Normalize"> 112 112 </transformationGroup> 113 - 81 + </extension> 82 + <extension 83 + point="de.cau.cs.kieler.kico.transformation"> 114 114 <transformationMethod 115 115 class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation" 116 116 id="TRIGGEREFFECT" ... ... @@ -117,7 +117,10 @@ 117 117 method="transformTriggerEffect" 118 118 name="Transform Trigger and Effect"> 119 119 </transformationMethod> 120 - 90 + </extension> 91 + 92 + <extension 93 + point="de.cau.cs.kieler.kico.transformation"> 121 121 <transformationMethod 122 122 class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation" 123 123 id="SURFACEDEPTH" ... ... @@ -124,7 +124,10 @@ 124 124 method="transformSurfaceDepth" 125 125 name="Transform Surface Depth"> 126 126 </transformationMethod> 127 - 100 + </extension> 101 + 102 + <extension 103 + point="de.cau.cs.kieler.kico.transformation"> 128 128 <transformationGroup 129 129 id="ALL" 130 130 dependencies="CORE NORMALIZE" ... ... @@ -133,13 +133,12 @@ 133 133 </extension> 134 134 {{/code}} 135 135 136 - \\112 + 137 137 138 138 == Compilation == 139 139 140 140 Once a bunch of model transformations are registered, these can simply be called using the KiCo central "KielerCompiler" class with its method compile(). This will be given a List<String> of transformation IDs or a comma separated String of transformation IDs as the first parameter. The second parameter is the EObject that is being transformed. It should meet the signature of the first model transformation called. Note that the actual model transformations that are done may vary because KiCo will automatically inspect the dependencies of each transformation requested (deep-recursively). If you do not like this to happen as an advanced user you can use a third parameter that will skip this autocompletion. Note that if you switch this off also NO transformation groups can be processed. Here is an overview and examples how to use the compile() method: 141 141 142 -(% class="wrapped" %) 143 143 |=((( 144 144 Method 145 145 )))|=((( ... ... @@ -196,208 +196,3 @@ 196 196 197 197 198 198 {{/code}} 199 - 200 -=== Requirement Completion === 201 - 202 -\\ 203 - 204 -(% class="wrapped" %) 205 -|=((( 206 -(% class="content-wrapper" %) 207 -((( 208 -(% style="text-align: center;" %) 209 -Original 210 - 211 -(% class="wrapped" %) 212 -|=((( 213 -(% class="content-wrapper" %) 214 -((( 215 - [[image:attach:dependencies2.jpg]] 216 - 217 -(% style="text-align: center;" %) 218 -Original Dependency 219 -Graph 220 -))) 221 -)))|=((( 222 -(% class="content-wrapper" %) 223 -((( 224 -(% style="text-align: center;" %) 225 -[[image:attach:dependencies3.jpg]] 226 - 227 -(% style="text-align: center;" %) 228 -Two alternative 229 -transformation 230 -implementations 231 -for Abort 232 -))) 233 -))) 234 - 235 -\\ 236 -))) 237 -)))|=((( 238 -(% class="content-wrapper" %) 239 -((( 240 -(% style="text-align: center;" %) 241 -Example 1 242 - 243 -(% class="wrapped" %) 244 -|=((( 245 -(% class="content-wrapper" %) 246 -((( 247 - [[image:attach:dependencies4.jpg]] 248 - 249 -(% style="text-align: center;" %) 250 -Selected for 251 -transformation 252 -))) 253 -)))|=((( 254 -(% class="content-wrapper" %) 255 -((( 256 - [[image:attach:dependencies4b.jpg]] 257 - 258 -(% style="text-align: center;" %) 259 -Auto selected 260 -requirements 261 -))) 262 -))) 263 - 264 -\\ 265 -))) 266 -))) 267 - 268 -\\ 269 - 270 -\\ 271 - 272 -(% class="wrapped" %) 273 -|=((( 274 -(% class="content-wrapper" %) 275 -((( 276 -(% style="text-align: center;" %) 277 -Example 2 278 - 279 -(% class="wrapped" %) 280 -|=((( 281 -(% class="content-wrapper" %) 282 -((( 283 -[[image:attach:dependencies5.jpg]] 284 - 285 -(% style="text-align: center;" %) 286 -Selected for 287 -transformation 288 -))) 289 -)))|=(% style="text-align: center;" %)(% style="text-align: center;" %) 290 -((( 291 -(% class="content-wrapper" %) 292 -((( 293 -[[image:attach:dependencies5b.jpg]] 294 - 295 -Auto selected 296 -requirements 297 -using DEFAULT 298 -of alternative 299 -group 300 - 301 -\\ 302 -))) 303 -))) 304 - 305 -\\ 306 -))) 307 -)))|=((( 308 -(% class="content-wrapper" %) 309 -((( 310 -(% style="text-align: center;" %) 311 -Example 3 312 - 313 -(% class="wrapped" %) 314 -|=((( 315 -(% class="content-wrapper" %) 316 -((( 317 -[[image:attach:dependencies6.jpg]] 318 - 319 -(% style="text-align: center;" %) 320 -Selected for 321 -transformation 322 -))) 323 -)))|=((( 324 -(% class="content-wrapper" %) 325 -((( 326 -[[image:attach:dependencies6b.jpg]] 327 - 328 -(% style="text-align: center;" %) 329 -Auto selected 330 -requirements 331 -using selected 332 -alternative 333 -))) 334 -))) 335 - 336 -\\ 337 -))) 338 -))) 339 - 340 -\\ 341 - 342 -== Help / Problems / FAQs == 343 - 344 -Maybe you get into problems when using KiCo. The following list should give you hints to solve these. If you have a problem not considered here please write us an e-mail (see above for contact information of the persons in charge of KiCo). 345 - 346 -(% class="wrapped" %) 347 -|=((( 348 -Symptom 349 -)))|=((( 350 -Reason 351 -)))|=((( 352 -Solution 353 -))) 354 -|((( 355 -You get the following run time error: 356 - 357 - 358 -\\\\\\\\\\\\\\\\[[java:102>>url:http://java:102||shape="rect"]] 359 -[[java:136>>url:http://java:136||shape="rect"]] 360 -[[java:164>>url:http://java:164||shape="rect"]]\\ 361 - 362 -{{{ENTRY de.cau.cs.kieler.klighd 4 0 2014-03-17 11:08:46.009!MESSAGE !STACK 0java.lang.RuntimeException: Cannot find a transformation with the ID 'ABORT2'. Make sure that the transformation with this ID is registered and its declaring plugin is loaded. Make sure that the ID does exactly match (case sensitive). Maybe you forgot to separate multiple ID's by a comma. at de.cau.cs.kieler.kico.KielerCompiler.getTransformation(KielerCompiler.java:61) at de.cau.cs.kieler.kico.KielerCompiler.getDependencies(KielerCompiler.java:82) at de.cau.cs.kieler.kico.KielerCompiler.isDependingOn(KielerCompiler.) at de.cau.cs.kieler.kico.KielerCompiler.insertTransformationID(KielerCompiler.) at de.cau.cs.kieler.kico.KielerCompiler.expandDependencies(KielerCompiler.)...}}} 363 -)))|((( 364 -There is a transformation with ID "ABORT2" referenced 365 -either by the initial call to KielerCompiler.compile() or 366 -by some of the dependent transformations / 367 -transformation group. 368 - 369 -But KiCo could not find any registered transformation 370 -with ID "ABORT2". 371 - 372 -Maybe the plugin declaring "ABORT2" was not loaded 373 -or the ID is misspelled. 374 - 375 -\\ 376 -)))|((( 377 -Check why "ABORT2" may not be found 378 -by KiCo, more specifically, check if the 379 -declaring can be loaded (sometimes 380 -compiler error prevent it from being loaded 381 -or it has unsatisfied dependencies). 382 -Also check the spelling of the ID, maybe 383 -the declaring plugin defines the transformation 384 -with the ID "abort2". 385 -))) 386 -|((( 387 -You get the following error: 388 - 389 -{{{!ENTRY de.cau.cs.kieler.kico 2 2 2014-03-17 11:26:13.818}}} 390 - 391 -\\ 392 - 393 -{{{!MESSAGE Extension 'TERMINATION' from component: de.cau.cs.kieler.sccharts cannot beloaded becaus this ID is already taken. (de.cau.cs.kieler.kico)}}} 394 -)))|((( 395 -The trasformation with ID "TERMINATION" is already 396 - registered and this ID cannot be used a second time. 397 -The component "de.cau...sccharts" tries to register 398 -a transformation with this ID while this ID is already 399 -taken. 400 -)))|((( 401 -Rename one of the IDs or form a group of 402 - transformations. 403 -)))
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 - 508232761 +9470066 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/ 50823276/Kieler Compiler1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470066/Kieler Compiler (KiCo)