Summary: | [GTK] Compiler flags for optimization | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Alp Toker <alp> | ||||
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | berto, mjs, mrowe | ||||
Priority: | P2 | Keywords: | Gtk, Performance | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Attachments: |
|
Description
Alp Toker
2007-12-04 20:51:05 PST
We build with -fomit-frame-pointer disabled on the Mac as it makes backtraces from production builds next-to-useless. Our measurements show it'd be approximately 5% speedup on the JS iBench though. Created attachment 17742 [details]
Optimization flags
The biggest problem with this patch is that -fstrict-aliasing in JavaScriptCore.pri ends up affecting the whole build and getting applied to WebCore, which is not correct. We only want it to apply to JSC.
-fno-exceptions -fno-rtti landed in r28651. Other flags still up for discussion. Old bug, I'm closing it as it's no longer relevant, the flags discussed here are either already present or implicitly defined by -O2. |