RESOLVED FIXED 55051
Consider turning off frame pointer omission (FPO) for all builds on Windows 
https://bugs.webkit.org/show_bug.cgi?id=55051
Summary Consider turning off frame pointer omission (FPO) for all builds on Windows
Adam Roben (:aroben)
Reported 2011-02-23 08:42:16 PST
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.
Attachments
Add attachment proposed patch, testcase, etc.
Adam Roben (:aroben)
Comment 1 2011-02-23 09:07:12 PST
<rdar://problem/9042198>
Brent Fulgham
Comment 2 2022-02-11 14:50:04 PST
Our builds already do this.
Note You need to log in before you can comment on or make changes to this bug.