https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71567
--- Comment #8 from Artem <tyoma.ariv at gmail dot com> --- (In reply to Manuel López-Ibáñez from comment #7) > See https://gcc.gnu.org/wiki/FAQ#misoptimization > > and https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#Warning-Options Thank you for the links. However I am not able to find compilation keys to indicate initial problem. Could you please provide an example when -Waggressive-loop-optimizations returns warning? You say that solution with using -fno-aggressive-loop-optimizations does not guaranty correct compilation. Maybe switch off optimization at all could help to avoid problems related to "undefined behavior" during optimization. Could you please, advise. I understand that source code will be broken but it have already worked correctly for many years with xlC compiler.
