Re: Optimization techniques

Gene Wirchenko <genew@telus.net>
Tue, 30 Apr 2019 18:24:17 -0700

          From comp.compilers

Related articles
[26 earlier articles]
Re: Optimization techniques 0xe2.0x9a.0x9b@gmail.com (2019-04-27)
Re: Optimization techniques haberg-news@telia.com (Hans Aberg) (2019-04-27)
Re: Optimization techniques david.brown@hesbynett.no (David Brown) (2019-04-28)
Re: Optimization techniques david.brown@hesbynett.no (David Brown) (2019-04-28)
Re: Optimization techniques genew@telus.net (Gene Wirchenko) (2019-04-30)
Re: Optimization techniques genew@telus.net (Gene Wirchenko) (2019-04-30)
Re: Optimization techniques genew@telus.net (Gene Wirchenko) (2019-04-30)
Re: Optimization techniques david.brown@hesbynett.no (David Brown) (2019-05-01)
Re: Optimization techniques david.brown@hesbynett.no (David Brown) (2019-05-01)
Re: Optimization techniques martin@gkc.org.uk (Martin Ward) (2019-05-02)
Re: Optimization techniques 847-115-0292@kylheku.com (Kaz Kylheku) (2019-05-02)
Re: Optimization techniques 847-115-0292@kylheku.com (Kaz Kylheku) (2019-05-02)
Re: Optimization techniques and error detection genew@telus.net (Gene Wirchenko) (2019-05-03)
[3 later articles]
| List of all articles for this month |

From: Gene Wirchenko <genew@telus.net>
Newsgroups: comp.compilers
Date: Tue, 30 Apr 2019 18:24:17 -0700
Organization: A noiseless patient Spider
References: <72d208c9-169f-155c-5e73-9ca74f78e390@gkc.org.uk> 19-04-021 19-04-023 19-04-037
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="93002"; mail-complaints-to="abuse@iecc.com"
Keywords: design, comment
Posted-Date: 30 Apr 2019 22:22:08 EDT

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]


Post a followup to this message

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