55051 2011-02-23 08:42:16 -0800 Consider turning off frame pointer omission (FPO) for all builds on Windows 2022-02-11 14:50:04 -0800 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) PC Windows XP RESOLVED FIXED InRadar, PlatformOnly P2 Normal --- 1 aroben webkit-unassigned bfulgham sfalken oldest_to_newest 356107 0 aroben 2011-02-23 08:42:16 -0800 According to <http://blogs.msdn.com/b/yvesdolc/archive/2009/09/15/consider-not-using-the-frame-pointer-optimization-when-building-your-software.aspx> and the articles it links to, frame pointer omission (FPO) isn't a big performance win on Windows, and it makes a number of useful debugging tools (handle leak checking, memory leak detection, heap corruption detection) not work. It also makes it hard/impossible for profilers to capture accurate stack traces. Bug 54403 covers turning off FPO for Release (not Release_LTCG) builds, so that developers can reap these benefits without affecting customers. But we should do some benchmarking to see whether we can turn off FPO in Release_LTCG builds, too, without affecting performance. This would allow us to use these debugging/performance tools on customer builds, too. 356129 1 aroben 2011-02-23 09:07:12 -0800 <rdar://problem/9042198> 1840574 2 bfulgham 2022-02-11 14:50:04 -0800 Our builds already do this.