X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fdoc.texi;h=2fec1b47d43aeec9a21cdcc3e39809587ccc1322;hb=9fd03907adce1d0e3e31a8ce6be3e1547434ce40;hp=f3465fa1f4dedf696a2438a1124d5b5548a4e8f7;hpb=c574297b7acbcbf04d128113cf91dbbcc1730f9c;p=pintos-anon

diff --git a/doc/doc.texi b/doc/doc.texi
index f3465fa..2fec1b4 100644
--- a/doc/doc.texi
+++ b/doc/doc.texi
@@ -10,7 +10,9 @@ Your submission should have exactly one of each file, in the
 appropriate directory (e.g.@: for Assignment 1, place the files in the
 @file{threads} directory).  These files must be written in plain text
 format (not Microsoft Word, not PDF).  We recommend a text width of 65
-characters per line, with a hard limit of 80.
+characters per line, with a hard limit of 80.  If you use tab characters
+in your document files, be sure that your text editor's tab width is set
+to 8.
 
 @menu
 * README::                      
@@ -110,6 +112,21 @@ should be in @file{pintos/src/threads/testcases}.
 
 @item
 Think about what may actually crash your code.
+
+@item
+Think about what the compiler might do to your code.  Suppose you write
+the following to test your virtual memory implementation's ability to
+expand the stack:
+@example
+int main (void) @{
+  int array[4096];
+  array[123] = 234;
+  return 0;
+@}
+@end example
+@noindent The compiler is quite likely to notice that the value that you
+write to the array is never used again and thereby decide not to write
+it at all.  The result is that your test does not test anything at all.
 @end itemize
 
 Your @file{TESTCASE} file is also where you can show us the