Good catch. Probably not a common case as usually we're already in
supported type contexts when we get around to check range_compatible..
I guess it wouldn't hurt to put a gcc_checking_assert in
range_compatible_p to confirm that they are supported types before
returning true.
Certainly ok.
The range folding code of COND_EXPRs missed a check whether the
comparison operand type is supported.
Bootstrap and regtest in progress on x86_64-unknown-linux-gnu. I'll
push if that succeeds. There might be other places missing such
a check, not sure.
Richard.
PR tree-optimization/117
