http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59538
--- Comment #4 from Arsham Skrenes <arsham at skrenes dot com> --- Can I suggest then that GCC outputs a compiler warning when it removes a loop? It outputs warnings for unused variables as well as implicit casting, so why not have a warning for removing loops? Also, is there a directive that I can use to explicitly tell GCC to not remove a loop (without having to resort to a compiler flag which is global, printing a variable, or using the 'volatile' keyword which de-optimizes the caching of the target variable)? Thanks!
