Re: Optimization techniques

On Sun, 28 Apr 2019 23:49:53 +0200, David Brown
<david.brown@hesbynett.no> wrote:


[snip]


>If you are writing your code in a "C with the extra feature of having
>defined behaviour on signed integer overflow", and only compile it with
>suitable compilers (or compiler flags), then that's okay. But don't
>call it correct C code and blame compilers for your own mistakes or
>unwarranted assumptions.


          I would like to see it as part of the language. I *know* that I
want to have an error be thrown at run-time if an error can be
detected. (It is not an unwarranted assumption.) It is not as if
detecting signed integer overflow is a difficult thing on, for
example, System/370, which also dates from 1970.


          I am fine with compiler options allowing each of us to have our
respective ways. I am tired of the default being "Overflow happens;
too bad". That is why I refuse to use C. It is too dangerous for my
taste.


Sincerely,


Gene Wirchenko
[The overflow trap was in S/360 in 1963. It ain't new. -John]

Return to the comp.compilers page.
Search the comp.compilers archives again.