Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: gcc failure (optimised/non-optimised) Date: Mon, 24 Apr 2017 08:37:09 -0700 Organization: None to speak of Lines: 17 Message-ID: References: <58fb2265.5246218@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="b06baaefdd2d8c25f7a310fe1662b016"; logging-data="25672"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+d8iwML4P6eNa4JlxM+vXk" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:B86hQYz4t1Vo3zltZfdAIj28ffc= sha1:UCOEPMKf1GT60NIvtHnUm+q/dz0= Xref: csiph.com comp.lang.c:108408 James Harris writes: [...] > My view is similar to yours but not identical. I accept that a compiler > can achieve greater speed by making certain assumptions. What I would > want, though, is the compiler at least to say that it was doing > something which /could/ alter the behaviour. The problem is that, as I understand it, it's impractical to do that. I read an article a while ago from the authors of clang and/or llvm discussing the issue. I'll post a link when/if I find it again. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"