mal wrote:
> This is getting silly, really ;-)
indeed.
> Jumping out of loops is ok, but jumping back in is not: you can
> never know whether the optimizer rearranges the loop code, so
> jumping *into* loop constructs is not going to be portable.
sorry, but that's bullshit. if the optimizer cannot figure out where
basic blocks start and end, it's broken beyond repair.
quoting the ANSI C rationale:
"The Committee considered proposals for forbidding a goto into
a block from outside, since such a restriction would make possible
much easier flow optimization and would avoid the whole issue of
initializing auto storage (see =A73.1.2.4). The Committee rejected
such a ban out of fear of invalidating working code (however un-
disciplined) and out of concern for those producing machine-
generated C."
</F>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4