On Wed, Jan 13, 2010 at 11:00 AM, Peter Kasting <[email protected]> wrote: > On Wed, Jan 13, 2010 at 10:53 AM, Craig Schlenter > <[email protected]> wrote: >> >> I'm one try-server run away from possibly turning -fno-strict-aliasing on >> for >> all linux/bsd gcc: http://codereview.chromium.org/519034 >> >> From a "process" standpoint, given that there is some disagreement here >> is someone going to come find me with a clue bat if I commit this? > > I don't think anyone will be rabid :) > That said, my comment in my prior email stands: if we're basically capable > of throwing -fstrict-aliasing for first-party code now, what do we gain by > instead throwing -fno-strict-aliasing? I would be sad to see us do this > unless it really buys us something.
I believe it's just making the default setting explicit. PS: I'd be willing to flip the flag just after we do the next beta channel push and see how many more problems we get because of it. But in general, if it doesn't buy us any performance and it does cause hard-to-track-down crashes, I don't see why we should use it. The "correctness" gain doesn't buy us anything on other platforms anyway.
-- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
