http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59933
--- Comment #9 from Ian Hamilton ian at g0tcd dot com ---
Yes, that's all proper and correct. The invalid C code induces undefined
behaviour. I don't think anyone is disputing that.
However, to be pragmatic for a moment, the experience
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59933
--- Comment #13 from Ian Hamilton ian at g0tcd dot com ---
(In reply to Mark Warner from comment #11)
I'm confused .. what about..
for (k = i; k (int)(sizeof(NSQ_del_dec_struct) / sizeof(opus_int32)); ++k)
... is illegal or invalid ?
Why does
Assignee: unassigned at gcc dot gnu.org
Reporter: ian at g0tcd dot com
Created attachment 31979
-- http://gcc.gnu.org/bugzilla/attachment.cgi?id=31979action=edit
Small source file exhibiting the problem
If a for loop has some sort of error check to break out of the loop, which
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59933
Ian Hamilton ian at g0tcd dot com changed:
What|Removed |Added
CC||ian at g0tcd dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59933
--- Comment #3 from Ian Hamilton ian at g0tcd dot com ---
Just a thought.
Does ((int)(sizeof(NSQ_del_dec_struct) / sizeof(opus_int32)) correctly give you
the size of the sLPC_Q14 array?
From playing with my test case, it seems
