http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56932
--- Comment #4 from Kai Tietz <ktietz at gcc dot gnu.org> 2013-04-12 18:31:05 UTC --- 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?
