On Wed, Jan 13, 2010 at 9:42 AM, Evan Martin <e...@chromium.org> wrote: > With that in mind I think we should explicitly use > -fno-strict-aliasing until someone is willing to take the time to run > buildbots, track down regressions, etc.
+1 for "-fno-strict-aliasing until someone fixes most/all of the aliasing bugs, then switching to -fstrict-aliasing"
-- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev