> Am I right in thinking that the C standard says that this (casting a number > outside the range of the target) is "undefined behaviour" > As in the subtle bug is in perl Yes, this is what the C standard says. > does cast_i32 get defined or undefined by Configure on 5.005_03 on IA64? > If it's defined, does forcing it to be undefined make 5.005_03 "happy" ? The actual flag that matters is d_castneg. It gets undefined, so the code in util.c is called. That code, though, is "wrong" in 5.005_03 and "right" in 5.6.1 TRIAL 2. However, adding the tests to bop.t is probably a good idea. JeffThread Previous