summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2020-05-02 20:05:15 -0400
committerDaniel Micay <danielmicay@gmail.com>2020-05-02 20:05:15 -0400
commitfd001ac649f21e67872fd81932ea2329fb846488 (patch)
treedd828b75df92737fd795a444ee1da4ace7fbc553
parent38e18a6c6072e24a60c107c151b6230e65439f0b (diff)
explain when and why peak memory usage happens
-rw-r--r--static/build.html5
1 files changed, 4 insertions, 1 deletions
diff --git a/static/build.html b/static/build.html
index e7f7dcf8..66a154e9 100644
--- a/static/build.html
+++ b/static/build.html
@@ -195,7 +195,10 @@
partially supports it)</li>
<li>Android Open Source Project build dependencies</li>
<li>Linux kernel build dependencies</li>
- <li>16GiB of memory or more</li>
+ <li>16GiB of memory or more. Link-Time Optimization (LTO) creates huge peaks
+ during linking and is mandatory for Control Flow Integrity (CFI). Linking
+ Vanadium (Chromium) and the Linux kernel with LTO + CFI are the most memory
+ demanding tasks.</li>
<li>300GiB of free storage space</li>
</ul>