Comment #2 on issue 17103 by kmilli...@chromium.org: Review ARRAY_VS_SINGLETON defects reported by Coverity. http://code.google.com/p/chromium/issues/detail?id=17103
I have visited all the ARRAY_VS_SINGLETON defects in the V8 component and classified them. Some of them were false positives---we treated (the address of) a stack-allocated object as a one-element array. Nevertheless, I have fixed them by restructuring the code to avoid the defect reports. The others are intentional---we do pointer arithmetic on the address of stack- allocated objects in order to guard against stack overflow during possibly-deep recursion (e.g., parsing, compilation). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
