http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56932
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-04-12 19:00:02 UTC --- (In reply to comment #4) > Well, indeed increasing the array-size helps to avoid this issue. > Nevertheless > I don't get why it produces wrong code for argument of call of function t > here. > That there is a out-of-bounds access is one thing, but there is still wrong > code produced. Also why - if gcc already detects an out-of-bounds access - > there is no warning for that? There should be a warning that was added before 4.8 was released (Jakub knows more about it and maybe even why the warning in this case is not happening).
