On Wed, Jan 13, 2010 at 11:22 AM, Craig Schlenter < [email protected]> wrote:
> Other than the immediate gain of "hiding" crbug.com/28749, > Which you have a patch (actually two, but one with r+) for, right? > I think the biggest > benefit is that end users relying on 4.4 builds are likely to have a more > stable > experience in future since it is a safe default. I don't understand what you mean. Whichever way we set the flag, we'll be compiling with it. So that will be the "safe" thing for others to compile us with. Throwing -fstrict-aliasing has the added advantage that it makes _both_ settings "safe". > The other thing it buys us is a more relaxed timetable to solve the > aliasing > problems if it doesn't break the tree by default. Do we have other aliasing problems? If so my opinion changes. PK
-- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
