* Add a few stub sections.

diff --git a/Report/Main/Problems/Challenges.tex b/Report/Main/Problems/Challenges.tex
index 60a930e3babc391968a7aa54585993d0f1651ebb..fecab593a4d5000f70f2a3a6cb7a4a5520165007 100644 (file)
--- a/Report/Main/Problems/Challenges.tex
+++ b/Report/Main/Problems/Challenges.tex
@@ -86,6 +86,22 @@ informally expressed and discussed, and only added to the specification after
 being succesfully implemented. This is conforming to the incremental development
 of MontiumC that was envisioned at the outset of its development.
 
+\subsection{Familiarizing with LLVM}
+This section says something about integrating in the LLVM community as well as
+getting acquainted with the code.
+
+\subsection{Coding}
+This section says something about the challenges encountered while actually
+writing code, if I can think of enough things to say here.
+
+\subsection{Working together}
+This section says something about working with colleagues in various ways.
+
+\subsection{Staying generic}
+This section says something about the challenge of writing generic code:
+(changes to) transformations that are useful for both LLVM (ie on regular
+architectures) as well as for Recore (on the Montium).
+
 \subsection{Pipelined scheduling}
 I've also been involved for a bit with the instruction scheduling algorithm
 required for the new (pipelined) hardware design. Even though this is completely