Path: csiph.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Gene Wirchenko Newsgroups: comp.compilers Subject: Re: Optimization techniques Date: Tue, 30 Apr 2019 18:24:17 -0700 Organization: A noiseless patient Spider Lines: 26 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <19-04-052@comp.compilers> References: <72d208c9-169f-155c-5e73-9ca74f78e390@gkc.org.uk> <19-04-021@comp.compilers> <19-04-023@comp.compilers> <19-04-037@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit 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 X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:2236 On Sun, 28 Apr 2019 23:49:53 +0200, David Brown 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]