[SPCA] Asm intro

semester3/spca/parts/01_c/03_memory/01_allocation.tex

@@ -12,7 +12,6 @@ it's just that the \textit{compiler} and not the programmer decides when to allo
 \content{Goals} The allocation should have the highest possible throughput and at the same time the best (i.e. lowest) possible memory utilization.
 This however is usually conflicting, so we have to balance the two.
 
-\numberingOff
 \inlinedef \bi{Aggregate payload} $P_k$: All \texttt{malloc}'d stuff minus all \texttt{free}'d stuff
 
 \inlinedef \bi{Current heap size} $H_k$: Monotonically non-decreasing. Grows when \texttt{sbrk} system call is issued.

semester3/spca/parts/01_c/03_memory/03_pitfalls.tex

@@ -12,4 +12,4 @@ Some of these bugs (especially bad references) can usually be found using a debu
 
 Substitute \texttt{malloc} with a \texttt{malloc} that has extra checking code (like \texttt{UToronto CSRI malloc} to detect memory leaks)
 
-Using \texttt{valgrind} (a memory debugger). Or, simply don't bother with \lC\ and use \texttt{Rust}.
+Another option is using \texttt{valgrind} (a memory debugger). Or, simply don't bother with \lC\ and use \texttt{Rust}.