-> for gnu classpath absolutely necessary
-> estimated effort: unknown
+(l) replace signals with "nice traps"?
+ pro -> don't rely on operating system anymore
+ pro -> maybe better ghci behaviour?
+ cons -> at some point, signals are useful for debugging?
+ cons -> better "template" tricks are needed, as we cannot insert more
+ instructions or want to place nop's at production code path
+
(l) gnu classpath integration
-> would be awwwesome
-> depends on: exceptions, jni (?)
-> estimated effort: unknown
+(m) hoopl
+ -> for "frontEnd analysis"
+ -> transition to MIR (Mate IR)?
+
+(h) switch statement (basically lookupswitch insn)
+
(m) testing: hunit? quickcheck? other?
-> we have `make tests' now, but it should be only considered as
high-level test. we need something
(l) check different types (byte, long, ...)
-(l) get rid of CUInt where appropriate
- -> CPtrdiff and CSize (ptrdiff_t and size_t) is more portable
-
(l) floating point support
(h) better code generation
(l) get rid of missingh
-> huge dependency and we just need one function of it
+(l) get more details what takes time
+ -> use Data.Time.Clock
+ -> seperate analysis, jit, execution, ...
+ -> maybe use ghc profiling? (it doesn't measure native execution, but well)
+
+(l) testing
+ -> specjvm98
+ -> dacapo benchmark suite
+
(l) ... low priority
(m) ... medium priority