 |
 |
This is the typical problem with array bounds checking in gcc. It's pretty brain dead because, as you can see, k is set to 0 right before the loop; so there is absolutely no chance that the array will be indexed incorrectly. Unfortunately, gcc has roughly a one source line window for analysis, making this check pretty useless and that is why we do not compile with array bounds checking.We do look at Coverity analysis which does a much better job at catching this.
—
Reply to this email directly or view it on GitHub.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1