-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathpaper-no-comments.tex
121 lines (97 loc) · 3.28 KB
/
paper-no-comments.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
\documentclass[submission,copyright,creativecommons]{eptcs}
\providecommand{\event}{ACL2 Workshop 2017} % Name of the event you are submitting to
% \usepackage{breakurl} % Not needed if you use pdflatex only.
\usepackage{amsmath,amssymb,amsfonts,amsthm}
\usepackage{fancyvrb}
% so we can use \-/ for breakable dashes in long names
\usepackage[shortcuts]{extdash}
% \usepackage{bigfoot}
% \usepackage{tikz}
\usepackage{color}
\usepackage{framed}
% \newtheorem{theorem}{Theorem}
% \newtheorem{corollary}{Corollary}
% The first of the following two definitions of the comment
% environment is adapted from
% http://tex.stackexchange.com/questions/71371/how-to-change-color-in-an-environment
% while the second comes from a package. Choose the first to see
% comments and the second to hide them.
%%%\newenvironment{comment}
%%% {\par\medskip
%%% \color{red}%
%%% \begin{framed}
%%% \ignorespaces}
%%% {\end{framed}
%%% \medskip}
\usepackage{comment}
% Neither of the following worked for me:
%\newenvironment{mycomment}{{\begin{comment}}}{{\end{comment}}}
% \let\mycomment\comment
% \let\endmycomment\endcomment
\usepackage{listings}
\lstset{ %
basicstyle=\normalsize\ttfamily,
language=lisp,
columns=fullflexible,
escapeinside={\<}{\>},
}
\newcommand*{\var}[1]{\mathit{#1}}
\title{Meta-extract}
\author{Matt Kaufmann
\institute{Department of Computer Science\\
The University of Texas at Austin\\
Austin, TX, USA}
\email{[email protected]}
\and
Sol O. Swords
\institute{Centaur Techology, Inc.\\
Austin, TX, USA}
\email{[email protected]}
}
\def\titlerunning{Meta-extract}
\def\authorrunning{M. Kaufmann \& S. Swords}
\begin{document}
\maketitle
\begin{abstract}
ACL2 has long supported user-defined simplifiers, so-called {\em
metafunctions} and {\em clause processors}, which are installed
when corresponding rules of class {\tt :meta} or {\tt
:clause-processor} are proved correct. Historically, such
simplifiers could access the logical world at execution time and
could call certain built-in proof tools, but could not assume the
soundness of the proof tools or the truth of any facts extracted
from the world or context when proving a simplifier correct. Starting with
ACL2 Version 6.0, released in December 2012, an additional
capability was added which allows the correctness proofs of
simplifiers to assume the correctness of some such proof tools and
extracted facts. In this paper we explain this capability and give
examples that demonstrate its utility.
\end{abstract}
\section{Introduction}
\label{sec:intro}
\input{intro}
\section{Meta-extract}
\label{sec:meta-extract}
\input{meta-extract}
\section{Using ``meta-extract-user.lisp''}
\label{sec:user}
\input{wrapper}
\section{Applications}
\label{sec:applications}
\input{applications}
% No related work section; see top of related.tex
% \section{Related Work}
% \label{sec:related}
% \input{related}
\section{Conclusion}
\label{sec:conclusion}
\input{conclusion}
\section*{Acknowledgments}
% Matt had some chats with J about this stuff back in 2012.
We thank J Moore for helpful discussions.
Preparation of this paper was partially supported by DARPA under
Contract No. FA8750-15-C-0007 (subcontract 15-C-0007-UT-Austin).
% \nocite{*}
\bibliographystyle{eptcs}
\bibliography{paper}
\end{document}