[Webkit-unassigned] [Bug 55051] New: Consider turning off frame pointer omission (FPO) for all builds on Windows

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=55051

           Summary: Consider turning off frame pointer omission (FPO) for
                    all builds on Windows
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Keywords: NeedsRadar, PlatformOnly
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: aroben at apple.com
                CC: sfalken at apple.com


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.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.