Dan Kegel wrote:
> On Wed, Jan 13, 2010 at 9:12 AM, Stephen White <senorbla...@chromium.org>
> wrote:
>> 2) Most of the supposed performance advantage of strict aliasing rules is
>> probably taken care of by memory disambiguation in modern (ie., Core2 and
>> later) CPUs.
>
> I kind of doubt that. Disallowing aliasing lets the compiler do
> a number of high-level optimizations that the chip could never do on its own.
> See e.g.
> http://cellperformance.beyond3d.com/articles/2006/06/understanding-strict-aliasing.html
>
> I'm for -fstrict-aliasing except for third_party.
Me too.
I support -fstrict-aliasing or not specifying anything explicitly (as
we presently do), and only using -fno-strict-aliasing for specific
third_party libraries that are known to need it.
Mark
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
