Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."

[Robert Dewar]

(again I apologize for breaking the thread),
Here is the reply I sent properly threaded

Gaby said

> K&R C leaves arithmetic overflow undefined (except for unsigned
> types), in the sense that you get whatever the underlying hardware
> gives you.  If it traps, you get trapped.  If it wraps, you get > 
wrapped.

Is that really what the K&R book says, or just what compilers typically
did? My memory is that the K&R book leaves it undefined period, but it's
a long time since I read it!