Comment #30 on issue 28749 by craig.schlen...@chromium.org: gcc 4.4-specific renderer crash in malloc, memory corruption while loading plugins (?) http://code.google.com/p/chromium/issues/detail?id=28749
I had considered using a union to avoid the aliasing issue but apparently when using classes in unions, the class must have a trivial constructor (see http://www.open- std.org/jtc1/sc22/wg21/docs/papers/2007/n2248.html) which seems a bit restrictive. The other option would be bit_cast (base/basictypes.h) but that probably won't work properly for non-POD types :( I'm not opposed to using no_strict_aliasing = 1 but I thought the long term plan was to try to fix aliasing errors. I could arguably just unset that locally and fix the regressions without having other users of the tree suffer through these issues. I will post a patch later ... -- 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
