+End of Execution Summary
+------------------------
+
+C11Tester prints summary statistics at the end of each execution. These
+summaries are based off of a few different properties of an execution, which we
+will break down here:
+
+* A _buggy_ execution is an execution in which C11Tester has found a real
+ bug: a data race, a deadlock, or a failure of a user-provided assertion.
+ C11Tester will only report bugs in feasible executions.
+
+
+Other Notes and Pitfalls
+------------------------
+
+* Data races may be reported as multiple bugs, one for each byte-address of the
+ data race in question. See, for example, this run:
+
+ $ ./run.sh test/releaseseq.o
+ ...
+ Bug report: 4 bugs detected
+ [BUG] Data race detected @ address 0x601078:
+ Access 1: write in thread 2 @ clock 4
+ Access 2: read in thread 3 @ clock 9
+ [BUG] Data race detected @ address 0x601079:
+ Access 1: write in thread 2 @ clock 4
+ Access 2: read in thread 3 @ clock 9
+ [BUG] Data race detected @ address 0x60107a:
+ Access 1: write in thread 2 @ clock 4
+ Access 2: read in thread 3 @ clock 9
+ [BUG] Data race detected @ address 0x60107b:
+ Access 1: write in thread 2 @ clock 4
+ Access 2: read in thread 3 @ clock 9
+
+
+See Also
+--------
+
+The C11Tester project page:
+
+> <http://demsky.eecs.uci.edu/c11tester.html>
+
+The C11Tester source and accompanying benchmarks on Gitweb:
+
+> <http://plrg.eecs.uci.edu/git/?p=c11tester.git>
+>
+> <http://plrg.eecs.uci.edu/git/?p=c11llvm.git>
+>
+> <http://plrg.eecs.uci.edu/git/?p=c11concurrency-benchmarks.git>
+
+
+
+Contact
+-------
+
+Please feel free to contact us for more information. Bug reports are welcome,
+and we are happy to hear from our users. We are also very interested to know if
+C11Tester catches bugs in your programs.
+
+Contact Weiyu Luo at <weiyul7@uci.edu> or Brian Demsky at <bdemsky@uci.edu>.
+
+
+Copyright
+---------
+
+Copyright © 2013 and 2019 Regents of the University of California. All rights reserved.
+
+C11Tester is distributed under the GPL v2. See the LICENSE file for details.
+
+
+Acknowledgments
+---------------
+
+This material is based upon work supported by the National Science
+Foundation under Grant Numbers 1740210 and 1319786 and Google Research
+awards.
+
+Any opinions, findings, and conclusions or recommendations expressed in
+this material are those of the author(s) and do not necessarily reflect
+the views of the National Science Foundation.
+