> This code only works for one-complement machines, since it assumes a > symmetric range for Int. It breaks when UI_To_Int returns Integer'First, as > it did in this case. When it does, the abs produces an erroneous result > (since checking is disabled). So it almost doesn't matter what it puts into > Num (but it actually puts in an out-of-range value there too).
Is there a simple way to have the Ada runtime (+ compiler) be built with checking enabled when bootstrapping? Thanks a lot, Duncan.
