Summary: | build failure after WebTextRenderer patch, uninitialized variables | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Justin Garcia <justin.garcia> | ||||||
Component: | Tools / Tests | Assignee: | mitz | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | ||||||||
Priority: | P1 | ||||||||
Version: | 420+ | ||||||||
Hardware: | Mac | ||||||||
OS: | OS X 10.4 | ||||||||
Attachments: |
|
Description
Justin Garcia
2005-12-19 18:40:59 PST
Created attachment 5169 [details]
Build fix
Sorry about the bug! Darin actually warned me about uninitialized variable
warnings in another part of that patch, but I didn't know that I have to test a
deployment build.
These initial values are never used: firstSmallCap is only used when isSmallCap
is true, and whenever isSmallCap is set to true, firstSmallCap is set;
substituteRenderer is only used if substituteLength > 0, in which case
substituteRenderer is set.
Comment on attachment 5169 [details]
Build fix
r=me
Created attachment 5189 [details]
fix more uninitialized variable warnings
These are the ones Darin warned me about. Why do they generate warnings only in
deployment configuration?
Apparently gcc warns about uninitialized variables when any sort of optimizations are turned on. Tim H. is looking into a way to turn these warnings on in Development mode w/o enabling optimizations. Comment on attachment 5189 [details]
fix more uninitialized variable warnings
r=me
|