https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64277
--- Comment #12 from Ilya Enkovich <enkovich.gnu at gmail dot com> --- (In reply to Richard Biener from comment #10) > Ick - that will also paper over good warnings so I'd rather not do that. I'm also worried about possible good warnings removal. Thus I disable them only in case cunroll speculates about iterations number and never disable them for the first loop iteration. I agree warnings disabling looks like a workaround. But it doesn't seem correct to complain on code generated by compiler and probably never executed. Each time maxiter is used for complete unroll following optimizations may improve maxiter estimation and thus we get a compiler generated dead code which still may produce warnings.
