On Wed, Jan 13, 2010 at 12:07 PM, Craig Schlenter <[email protected] > wrote:
> > Do we have other aliasing problems? If so my opinion changes. > > There are some aliasing issues still in play. Off the top of my head: > > 1. unit_tests has what might be an issue in stl_tree.h or a compiler issue > (bug filed with gcc ppl) and it was already using > -fno-strict-aliasing to avoid this with gcc 4.4. > 2. skia has an unresolved issue. Note the filing date: > http://code.google.com/p/skia/issues/detail?id=18 > 3. v8 has an aliasing issue in dtoa and somewhere else that I forget. > 4. there are issues in third party code of course eg. icu, webkit etc. 2-4 I'm not worried about because they're effectively third-party (even if they're done in-house), but 1 is an issue, and cases the compiler doesn't catch are issues. So it seems best to go ahead and turn off strict aliasing. I'd love to see us fix and enable it later. Not sure what will provide the motivation to do that. PK
-- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
