source: Papers/fopara2013/appendix.tex

Last change on this file was 3438, checked in by campbell, 7 years ago

Appendix about the reviewer's comments.

File size: 1.8 KB
1\section{Changes in response to the reviewer's comments}
5We have made more explicit reference to a key WCET survey paper, in
6particular noting that it is a useful source of information about
7commercial tools such as AbsInt.
9\item We have altered and improved the example to remove some
10distracting ambiguity and demonstrate a parametric time bound.  The
11text now identifies the added code by more than just its colour.  The
12later sections now refer back to the example to illustrate the effects
13of each technique.
16We've removed the paragraph on logic programming languages because one
17of the reviewers pointed out that standard Prolog may have the
18necessary features, which we haven't tried.  Thus we felt it was best
19not to claim anything about logic programming at this time.
22We have been more explicit about the type of code generated by the
23Lustre compiler, and what kinds of loop can be handled automatically
24by the Cost plugin and where loop iteration bounds come from.
26\item The structure of the document has been greatly improved.
27Section 2 has been restructured and broken up into subsections to give
28a clearer comparison of existing approaches with CerCo.
29Section 4 has been reorganised to highlight the connections between
30the different parts of the work and a short overview provided to help
31the reader understand the significance of each part of the work.
33\item A clearer distinction is made between the core contribution of
34the compiler --- which provides local cost information in the source
35code and thus is largely agnostic to how loops are structured and what
36kind of data structures are used --- and the cost synthesis work which
37provides higher-level costs using it.
39\item The text has been extensively revised to be easier to read, and
40to make minor corrections, including those identified by the reviewers.
Note: See TracBrowser for help on using the repository browser.