On 9 October 2013 11:02, vijay nag wrote: > Alright that is perfectly valid behaviour. Why does compiler consider > it to be a unsigned type at optimization level zero ? It doesn't. > i.e. I see a > wrap around after > -128 to 128 ? Because undefined behaviour.
