1 | % CerCo: Certified Complexity |
---|
2 | % |
---|
3 | % Addendum to Deliverable 6.2 |
---|
4 | % |
---|
5 | % Plan for Dissemination and Use |
---|
6 | % Addendum requested by project reviewers at end of year 1. |
---|
7 | % |
---|
8 | % Ian Stark |
---|
9 | % 2011-05 |
---|
10 | |
---|
11 | \documentclass[11pt,a4paper]{article} |
---|
12 | \usepackage{../style/cerco} |
---|
13 | |
---|
14 | \hypersetup{bookmarksopenlevel=2} |
---|
15 | |
---|
16 | \title{ |
---|
17 | INFORMATION AND COMMUNICATION TECHNOLOGIES\\ |
---|
18 | (ICT)\\ |
---|
19 | PROGRAMME\\ |
---|
20 | \vspace*{1cm}Project FP7-ICT-2009-C-243881 {\cerco}} |
---|
21 | |
---|
22 | \date{ } |
---|
23 | \author{} |
---|
24 | |
---|
25 | \begin{document} |
---|
26 | \thispagestyle{empty} |
---|
27 | |
---|
28 | \vspace*{-1cm} |
---|
29 | \begin{center} |
---|
30 | \includegraphics[width=0.6\textwidth]{../style/cerco_logo.png} |
---|
31 | \end{center} |
---|
32 | |
---|
33 | \begin{minipage}{\textwidth} |
---|
34 | \maketitle |
---|
35 | \end{minipage} |
---|
36 | |
---|
37 | |
---|
38 | \vspace*{0.5cm} |
---|
39 | \begin{center} |
---|
40 | \begin{LARGE} |
---|
41 | \bf |
---|
42 | Addendum to Deliverable 6.2\\[\jot] |
---|
43 | Future Dissemination Plans |
---|
44 | \end{LARGE} |
---|
45 | \end{center} |
---|
46 | |
---|
47 | \vspace*{2cm} |
---|
48 | \begin{center} |
---|
49 | \begin{large} |
---|
50 | Version 1.0 |
---|
51 | \end{large} |
---|
52 | \end{center} |
---|
53 | |
---|
54 | \vspace*{0.5cm} |
---|
55 | \begin{center} |
---|
56 | \begin{large} |
---|
57 | Main Authors:\\ |
---|
58 | I. Stark |
---|
59 | \end{large} |
---|
60 | \end{center} |
---|
61 | |
---|
62 | \vspace*{\fill} |
---|
63 | \noindent |
---|
64 | Project Acronym: {\cerco}\\ |
---|
65 | Project full title: Certified Complexity\\ |
---|
66 | Proposal/Contract no.: FP7-ICT-2009-C-243881 {\cerco}\\ |
---|
67 | |
---|
68 | \clearpage \pagestyle{myheadings} \markright{{\cerco}, FP7-ICT-2009-C-243881} |
---|
69 | |
---|
70 | \tableofcontents |
---|
71 | |
---|
72 | \section{Premise} |
---|
73 | Deliverable~6.2, the \emph{Plan for the Use and Dissemination of Foreground} |
---|
74 | was submitted as the first report of the {\cerco} project. Following the |
---|
75 | scientific review of the project at the end of its first year, the reviewers |
---|
76 | recommended preparation of an addendum to specifically list future |
---|
77 | dissemination plans. This is that addendum. |
---|
78 | |
---|
79 | |
---|
80 | \section{Dissemination Plans} |
---|
81 | |
---|
82 | The {\cerco} project represents an unprecedented effort to create a |
---|
83 | machine-verified chain of trust for analysing program performance properties |
---|
84 | through compilation. This combines novel work in the theory of machine proof |
---|
85 | and certified compilation with its concrete application to a specific |
---|
86 | industrial microcontroller. |
---|
87 | |
---|
88 | As appropriate for a project in the \emph{Future and Emerging Technologies} |
---|
89 | programme, a major target for dissemination is to influence future work by |
---|
90 | other European research groups, through a direct demonstration of a verified |
---|
91 | resource-aware compiler. The immediate routes for this are the standard ones |
---|
92 | for academic communication and training: conference papers, journal articles, |
---|
93 | collaborative workshops, tutorial events. In addition, with the project |
---|
94 | centred around a substantial implementation effort, the compiler code and the |
---|
95 | machine proofs are themselves vehicles for dissemination to other researchers. |
---|
96 | |
---|
97 | The longer-term dissemination targets are the potential end-users of verified |
---|
98 | compiler technology: programmers of commodity microcontrollers being used in |
---|
99 | tightly resource-constrained embedded applications --- particularly those |
---|
100 | where safety-critical requirements mandate a high quality of performance |
---|
101 | certification. Possible routes for this long-term dissemination are through |
---|
102 | research symposia at industrially-relevant conferences, and tutorial sessions |
---|
103 | at conferences or other events with significant industrial presence. |
---|
104 | |
---|
105 | \subsection{Conferences and Workshops} |
---|
106 | |
---|
107 | We propose to submit results of {\cerco} research for presentation at |
---|
108 | appropriate international venues. There are very many conferences dealing |
---|
109 | with {\cerco}-related areas: compilation technology, machine-assisted proof, |
---|
110 | resource analysis, etc. For example, the following are particularly close to |
---|
111 | {\cerco} activity: |
---|
112 | \begin{itemize} |
---|
113 | \item CPP: Certified Programs and Proofs |
---|
114 | \item FMCAD: Formal Methods in Computer-Aided Design |
---|
115 | \item LOLA: Syntax and Semantics of Low-Level Languages |
---|
116 | \item VSTTE: Verified Software: Theories, Tools and Experiments |
---|
117 | \item SSV: Systems Software Verification |
---|
118 | \item FORMATS: Formal Modeling and Analysis of Timed Systems |
---|
119 | \item ITP: Interactive Theorem Proving (was TPHOLs) |
---|
120 | \item PSI: Program Understanding |
---|
121 | \end{itemize} |
---|
122 | Beyond these, there are many high-quality general conferences which would also |
---|
123 | provide a good venue for publicising the results of the project. For example: |
---|
124 | \begin{itemize} |
---|
125 | \item POPL: Principles of Programming Languages |
---|
126 | \item LPAR: Logic for Programming, Artificial Intelligence and Reasoning |
---|
127 | \item CC: Compiler Construction |
---|
128 | \item FM: International Symposium on Formal Methods |
---|
129 | \item APLAS: Asian Symposium on Programming Languages and Reasoning |
---|
130 | \end{itemize} |
---|
131 | In addition to these subject-related events, {\cerco} will contribute to |
---|
132 | FET-organized activities, such as conferences, dedicated workshops, working |
---|
133 | groups and other meetings. |
---|
134 | |
---|
135 | |
---|
136 | \subsection{Journals} |
---|
137 | |
---|
138 | The project participants will publish papers and articles based on {\cerco} |
---|
139 | results in appropriate archival venues, throughout the duration of the |
---|
140 | project. Most of the conferences listed above have formal proceedings; |
---|
141 | several also have affiliated special issues in journals, for publishing |
---|
142 | extended versions of papers. In addition, we expect to submit free-standing |
---|
143 | articles to appropriate journals, such as: |
---|
144 | \begin{itemize} |
---|
145 | \item Journal of Automated Reasoning |
---|
146 | \item Journal of Formalized Reasoning |
---|
147 | \item Information and Computation |
---|
148 | \item Theoretical Computer Science |
---|
149 | \item Higher-Order and Symbolic Computation |
---|
150 | \item Communications of the ACM |
---|
151 | \item Science of Computer Programming |
---|
152 | \end{itemize} |
---|
153 | |
---|
154 | \subsection{Tutorials and Training} |
---|
155 | |
---|
156 | As established researchers, the project participants will give lectures and |
---|
157 | tutorials on {\cerco}-related research as part of their existing dissemination |
---|
158 | activity throughout the course of the project. However, in addition to this |
---|
159 | {\cerco} will organise specific training activities targeted at the scientific |
---|
160 | community, and at potential industrial stakeholders. These are formal |
---|
161 | deliverables of Work Package~6 in the project contract. To increase |
---|
162 | visibility, and promote attendance, we would affiliate any event with an |
---|
163 | existing conference or school. For example, a {\cerco} tutorial would much |
---|
164 | more effectively reach a suitable audience if given as part of an established |
---|
165 | summer school. It may also be appropriate to collaborate with related EU |
---|
166 | projects or research groups in management of such events. |
---|
167 | |
---|
168 | To benefit the most from {\cerco} project results, such events should take |
---|
169 | place in the final year of the project. We plan to identify appropriate |
---|
170 | venues during the second year of {\cerco}. |
---|
171 | |
---|
172 | \subsection{Artefacts} |
---|
173 | |
---|
174 | A significant part of {\cerco} is the implementation effort, with accompanying |
---|
175 | experience gained in developing and verifying a machine-checked resource-aware |
---|
176 | compiler. This gives rise to specific software artefacts, which other |
---|
177 | projects can learn from and build upon. All these will be made |
---|
178 | publically-available at project milestones, and form a notable route for |
---|
179 | dissemination of the project outcomes. The full report D6.2 describes in |
---|
180 | detail the target communities and potential users of this software; here we |
---|
181 | summarize. |
---|
182 | |
---|
183 | \subsubsection{Untrusted Cost-Annotating Compiler} |
---|
184 | |
---|
185 | This is a functional compiler from C to assembler, structured and instrumented |
---|
186 | to trace the evolution of high-level code fragments to low-level instruction |
---|
187 | sequences and match their execution costs. |
---|
188 | |
---|
189 | \subsubsection{Untrusted Compiler within Proof-Assistant} |
---|
190 | |
---|
191 | This will be an implementation of the CerCo cost-annotating compiler within |
---|
192 | the \emph{Matita} proof assistant. This takes the form of a formal |
---|
193 | specification of the compiler in the calculus of (co)inductive constructions, |
---|
194 | arranged in so as to be directly executable within \emph{Matita}. |
---|
195 | |
---|
196 | \subsubsection{Trusted Cost-Annotating Compiler} |
---|
197 | |
---|
198 | This is the final product of the {\cerco} project and brings together a number |
---|
199 | of distinct elements: |
---|
200 | \begin{itemize} |
---|
201 | \item An executable compiler which automatically annotates C source code with |
---|
202 | machine execution costs; |
---|
203 | \item A machine-certified proof that the compiler is functionally correct and |
---|
204 | that the automatic annotations exactly reflect low-level instruction costs; |
---|
205 | \item Extensions to the \emph{Matita} interactive proof engine to automate |
---|
206 | this substantial proof; |
---|
207 | \item Example integration of these low-level cost-annotations with high-level |
---|
208 | program analysis tools in the \emph{Frama-C} framework. |
---|
209 | \end{itemize} |
---|
210 | |
---|
211 | |
---|
212 | \end{document} |
---|
213 | |
---|
214 | % LocalWords: Sacerdoti Coen microcontroller FMCAD VSTTE TPHOLs LPAR Artefacts |
---|