Bug 55051
| Summary: | Consider turning off frame pointer omission (FPO) for all builds on Windows | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Adam Roben (:aroben) <aroben> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bfulgham, sfalken |
| Priority: | P2 | Keywords: | InRadar, PlatformOnly |
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
Adam Roben (:aroben)
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)
<rdar://problem/9042198>
Brent Fulgham
Our builds already do this.