diff options
| author | Wilrik de Loose <wilrik@wilrik.nl> | 2008-05-16 09:55:11 (GMT) |
|---|---|---|
| committer | Wilrik de Loose <wilrik@wilrik.nl> | 2008-05-16 09:55:11 (GMT) |
| commit | e4999f5859edc905f7db59b2865fe6b150974cbc (patch) | |
| tree | 7831d2b7584ca0a974144b89b90f75bdc95cc714 /report/chapter2.tex | |
| parent | 8338135af544bfa284a7cc45affc06ee6079f8c5 (diff) | |
| download | 2in25-e4999f5859edc905f7db59b2865fe6b150974cbc.zip 2in25-e4999f5859edc905f7db59b2865fe6b150974cbc.tar.gz 2in25-e4999f5859edc905f7db59b2865fe6b150974cbc.tar.bz2 | |
Report Joshua + Wilrik
Diffstat (limited to 'report/chapter2.tex')
| -rw-r--r-- | report/chapter2.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/report/chapter2.tex b/report/chapter2.tex index 2d1959b..3a8dd52 100644 --- a/report/chapter2.tex +++ b/report/chapter2.tex @@ -19,4 +19,4 @@ The compiler is used to analyze the worst-case execution path and preferred pree The preferred preemption points can also be determined by the programmer with the help of insertion of traps in the source code to monitor when tasks of higher priority are ready to run. The programmer would already have an intuition as to where the number of live caches is minimized. Using this method, preferred preemption points can also be determined. \\
-Considering the two methods, it is clear that using the compiler is a more systematic and transparent way of finding preemption points. In addition, preemption points found using a compiler will generally perform better because the analysis is more extensive. However, this analysis can also be performed manually as described above is a compiler cannot be used. \\
+Considering the two methods, it is clear that using the compiler is a more systematic and transparent way of finding preemption points. In addition, preemption points found using a compiler will generally perform better because the analysis is more extensive. However, this analysis can also be performed manually as described above is a compiler cannot be used.
|