The Esterel v5 21 System Manual - Courses

2.4. WHY COMPILATION MAY FAIL 21
2.4 Why Compilation May Fail
Compilation may fail for a variety of reasons.
• The program may have syntax errors, type-checking errors, or logically
inconsistent exclusion or implication relations. The error messages are
printed by strlic.
• The program may contain several modules calling each other in an
inconsistent ways (cyclic structure, type clashes, etc.). The error messages
are printed by iclc.
• The program may contain a statically instantaneous loop, i.e. a loop
with a potentially instantaneous path from loop to end loop. The
error message is printed by lcsc. The current compiler Esterel v5 21
can only handle statically loop-free programs defined in [1].
• The program may have a combinational cycle. In this case, if neither
option -I nor option -causal is specified, the program is rejected by
the scssc processor. A graphical error message can be visualized by
typing
esterel -cycles foo.strl
Use the -I or -causal options to compile cyclic programs.
All Esterel textual error messages have the same format. They can be
directly used by programming tools, such as the Emacs text editor, to point
to the location of the errors (the Emacs -X ‘ “next error” command
is used to jump from one error location to another). All Esterel graphical
error messages are reported using a variant of the xes simulator.
Internal error messages denote compiler bugs and should be reported to
esterel-bugs@sophia.inria.fr together with the result of the command
esterel -info.
and the Esterel source code if possible.
2.5 Sanity Checks
Three options of the esterel commands performs sanity checks on the
program. These checks should be performed before embedding a program.