X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fvm.texi;h=90d407d2bc5edd7bd04c7b35ca227488224f89c5;hb=08dca88aad1dca1e4b660783775a5d125ffc819c;hp=599539be86b905cfa54a071a34122cd69097e86a;hpb=ba073485946c2d0cf90fefd1c9bb9b3316fbfe33;p=pintos-anon

diff --git a/doc/vm.texi b/doc/vm.texi
index 599539b..90d407d 100644
--- a/doc/vm.texi
+++ b/doc/vm.texi
@@ -256,9 +256,7 @@ It is impossible to predict how large the stack will grow at compile
 time, so we must allocate pages as necessary.  You should only allocate
 additional pages if they ``appear'' to be stack accesses.  You must
 devise a heuristic that attempts to distinguish stack accesses from
-other accesses.@footnote{You might find it useful to know that the
-80@var{x}86 instruction @code{pusha} pushes all 8 registers (32 bytes)
-on the stack at once.}  Document and explain the heuristic in your
+other accesses.  Document and explain the heuristic in your
 design documentation.
 
 The first stack page need not be loaded lazily.  You can initialize it