Closed Bug 360378 Opened 19 years ago Closed 18 years ago

Investigate effect of -finline-limit=n on codesize and performance

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 409803

People

(Reporter: bzbarsky, Unassigned)

Details

(Keywords: perf)

It might be interesting to see how twiddling this frob in GCC affects our performance characteristics.
Keywords: perf
Whiteboard: [wanted-1.9]
Although there are places where we intentionally inline large functions because they're only called from one place. (Some character sink stuff in the string code comes to mind, although I'm not sure if that still exists.) I think we should really be avoiding writing large functions called from many places as inline functions.
so, i noticed this was a problem and filed bug 409803 - my fault for not finding this bug beforehand. :/ duping against that, since it's really about -finline-limit and friends, and there's some perf and codesize data in there.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.