On Sun, Jan 26, 2014 at 6:57 PM, Austin Seipp <[email protected]> wrote: > * Profiling could break. Or profiling GHC (but not other smaller > things) could break. > * Dynamic linking could break. > * Rarer configurations could break but only for some cases, e.g. > threaded + profiling. Or LLVM + Profiling, or LLVM + dynamic linking, > etc etc. > * Static linking for GHCi could break on platforms that now use > dynamic linking by default (as we saw happen when I broke it.) > * GHC may only expose certain faulty behavior at certain optimization > levels (both in bootstrapping itself and in the tests - so maybe > ./validate looks mostly OK, but -O2 is not.) > * Bootstrapping the build with different compilers may break (i.e. an > unintentional backwards incompatible change is introduced in the > stage1 build) > * Any of these could theoretically break depending on things like the > host platform. > * The testsuite runs 'fast' by default. It would need to run slowly > to potentially uncover more problems, but this greatly increases the > runtime.
Disregard all this, upon closer inspection I see you only wanted ./validate anyway.* :) * But it still will hurt more when you add in low-powered builders. -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/ _______________________________________________ ghc-devs mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-devs
