https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104789
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Rémi Verschelde from comment #4) > I'm not familiar with the term "bounded roo". I reduced the test case as > much as I could to focus on the minimal code that would trigger the warning > which seems to me like a false positive - is it not one? roo was a typo for too. The r and t are next to each other on the standard qwerty keyboard. Anyways I think the warning should be reworded to say might be writing instead of a definite. There is another bug talking about the wording too. Also the way I read the code in both the original and reduced testcase, without knowing how components' range, there could be a buffer overflow.
