diff --git a/_site/courses/verifcomp/index.html b/_site/courses/verifcomp/index.html index b4ab671..23eeccd 100644 --- a/_site/courses/verifcomp/index.html +++ b/_site/courses/verifcomp/index.html @@ -20,7 +20,7 @@

Verified Compilers and Multi-Language Software

Course -CS4910: Verified Compilers and Multi-Language Software +CS4910 (CRN 17946): Verified Compilers and Multi-Language Software Semester diff --git a/_site/pubs/2019/ccc.pdf b/_site/pubs/2019/ccc.pdf new file mode 100644 index 0000000..3318bf3 Binary files /dev/null and b/_site/pubs/2019/ccc.pdf differ diff --git a/_site/pubs/2019/ccc/index.html b/_site/pubs/2019/ccc/index.html new file mode 100644 index 0000000..0ffb568 --- /dev/null +++ b/_site/pubs/2019/ccc/index.html @@ -0,0 +1,65 @@ + + + + + The Next 700 Compiler Correctness Theorems (Functional Pearl). + + + + +
+

The Next 700 Compiler Correctness Theorems (Functional Pearl).

+ +

Daniel Patterson and Amal Ahmed.

+ +

paper and mechanized proofs.

+ +

Compiler correctness is an old problem, with results stretching back + beyond the last half-century. Founding the field, John McCarthy and James + Painter set out to build a "completely trustworthy compiler". And yet, + until quite recently, even despite truly impressive verification efforts, + the theorems being proved were only about the compilation of whole + programs, a theoretically quite appealing but practically unrealistic + simplification. For a compiler correctness theorem to assure complete + trust, the theorem must reflect the reality of how the compiler will be + used.

+

There has been much recent work on more realistic "compositional" + compiler correctness aimed at proving correct compilation of components + while supporting linking with components compiled from different + languages using different compilers. However, the variety of theorems, + stated in remarkably different ways, raises questions about what + researchers even mean by a "compiler is correct." In this pearl, we + develop a new framework with which to understand compiler correctness + theorems in the presence of linking, and apply it to understanding and + comparing this diversity of results. In doing so, not only are we better + able to assess their relative strengths and weaknesses, but gain insight + into what we as a community should expect from compiler correctness + theorems of the future.

+ +
+ + diff --git a/_site/pubs/2019/ccc/proofs.zip b/_site/pubs/2019/ccc/proofs.zip new file mode 100644 index 0000000..fc30fd5 Binary files /dev/null and b/_site/pubs/2019/ccc/proofs.zip differ diff --git a/pubs/2019/ccc.pdf b/pubs/2019/ccc.pdf new file mode 100644 index 0000000..3318bf3 Binary files /dev/null and b/pubs/2019/ccc.pdf differ diff --git a/pubs/2019/ccc/index.html b/pubs/2019/ccc/index.html new file mode 100644 index 0000000..0ffb568 --- /dev/null +++ b/pubs/2019/ccc/index.html @@ -0,0 +1,65 @@ + + + + + The Next 700 Compiler Correctness Theorems (Functional Pearl). + + + + +
+

The Next 700 Compiler Correctness Theorems (Functional Pearl).

+ +

Daniel Patterson and Amal Ahmed.

+ +

paper and mechanized proofs.

+ +

Compiler correctness is an old problem, with results stretching back + beyond the last half-century. Founding the field, John McCarthy and James + Painter set out to build a "completely trustworthy compiler". And yet, + until quite recently, even despite truly impressive verification efforts, + the theorems being proved were only about the compilation of whole + programs, a theoretically quite appealing but practically unrealistic + simplification. For a compiler correctness theorem to assure complete + trust, the theorem must reflect the reality of how the compiler will be + used.

+

There has been much recent work on more realistic "compositional" + compiler correctness aimed at proving correct compilation of components + while supporting linking with components compiled from different + languages using different compilers. However, the variety of theorems, + stated in remarkably different ways, raises questions about what + researchers even mean by a "compiler is correct." In this pearl, we + develop a new framework with which to understand compiler correctness + theorems in the presence of linking, and apply it to understanding and + comparing this diversity of results. In doing so, not only are we better + able to assess their relative strengths and weaknesses, but gain insight + into what we as a community should expect from compiler correctness + theorems of the future.

+ +
+ + diff --git a/pubs/2019/ccc/proofs.zip b/pubs/2019/ccc/proofs.zip new file mode 100644 index 0000000..fc30fd5 Binary files /dev/null and b/pubs/2019/ccc/proofs.zip differ