WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
32674
Fix link failure on LTCG builds on Windows for chromium port
https://bugs.webkit.org/show_bug.cgi?id=32674
Summary
Fix link failure on LTCG builds on Windows for chromium port
Marc-Antoine Ruel
Reported
2009-12-17 10:45:47 PST
Created
attachment 45090
[details]
Patch Reenable SVGAllInOne.cpp. This required some fixups. Namely, there was conflicts in constants between HTMLNames and SVGNames, and conflicts between static functions names. No new tests as functionality has not changed.
Attachments
Patch
(19.51 KB, patch)
2009-12-17 10:45 PST
,
Marc-Antoine Ruel
no flags
Details
Formatted Diff
Diff
Patch
(19.02 KB, patch)
2009-12-17 10:49 PST
,
Marc-Antoine Ruel
no flags
Details
Formatted Diff
Diff
Patch
(18.80 KB, patch)
2009-12-17 10:51 PST
,
Marc-Antoine Ruel
no flags
Details
Formatted Diff
Diff
Patch
(11.00 KB, patch)
2009-12-17 12:49 PST
,
Marc-Antoine Ruel
no flags
Details
Formatted Diff
Diff
Patch
(12.69 KB, patch)
2009-12-17 12:52 PST
,
Marc-Antoine Ruel
no flags
Details
Formatted Diff
Diff
Show Obsolete
(4)
View All
Add attachment
proposed patch, testcase, etc.
WebKit Review Bot
Comment 1
2009-12-17 10:46:32 PST
Attachment 45090
[details]
did not pass style-queue: Failed to run "WebKitTools/Scripts/check-webkit-style" exit_code: 1 WebCore/svg/SVGAllInOne.cpp:99: Alphabetical sorting problem. [build/include_order] [4] WebCore/svg/SVGAllInOne.cpp:105: Alphabetical sorting problem. [build/include_order] [4] WebCore/svg/SVGAllInOne.cpp:137: Alphabetical sorting problem. [build/include_order] [4] WebCore/svg/SVGAllInOne.cpp:138: Alphabetical sorting problem. [build/include_order] [4] WebCore/svg/SVGAllInOne.cpp:151: Alphabetical sorting problem. [build/include_order] [4] Total errors found: 5
Marc-Antoine Ruel
Comment 2
2009-12-17 10:49:58 PST
Created
attachment 45091
[details]
Patch
Marc-Antoine Ruel
Comment 3
2009-12-17 10:51:55 PST
Created
attachment 45092
[details]
Patch
WebKit Review Bot
Comment 4
2009-12-17 10:51:59 PST
Attachment 45091
[details]
did not pass style-queue: Failed to run "WebKitTools/Scripts/check-webkit-style" exit_code: 1 WebCore/svg/SVGAllInOne.cpp:152: Alphabetical sorting problem. [build/include_order] [4] Total errors found: 1
WebKit Review Bot
Comment 5
2009-12-17 10:52:17 PST
style-queue ran check-webkit-style on
attachment 45092
[details]
without any errors.
Eric Seidel (no email)
Comment 6
2009-12-17 11:04:20 PST
Comment on
attachment 45092
[details]
Patch Do we have a build-bot which uses this (or that will), otherwise this will certainly break again. This is kinda an ugly fix, but that's because any of the AllInOne filese are kinda hacks. What is a LTCG build? Why should we be prefixing the SVGNames which conflict with HTMLNames instead of the reverse? It seems that at least some of these changes need comments. Like the naming of mapSvgAttributeToCSSProperty should have a comment. maybe we should just share that code using StyledElement.h/StyledElement.cpp instead of renaming our copy? Or does the copy actually do something different in the SVG case? This looks fine, but would be nice to hear answers to above before landing. Better to leave the "Reviewed by" line as the default "Reviewed by NOBODY(OOPS!)" because our scripts like svn-apply, the commit-queue and normal bugzilla-tool land-diff/land-patches know how to fix that up with the proper reviewer from the bug anyway.
Eric Seidel (no email)
Comment 7
2009-12-17 11:05:51 PST
The chromium side of this was:
http://codereview.chromium.org/500099
and:
http://code.google.com/p/chromium/issues/detail?id=30494
Eric Seidel (no email)
Comment 8
2009-12-17 11:06:47 PST
It's possible that Apple's windows builders will want to use a similar optimization. CCing the Apple windows build folks.
Marc-Antoine Ruel
Comment 9
2009-12-17 11:20:04 PST
LTCG means link time code generation. SVGNames are the only one conflicting. I use the SVG ones because it is SVG compile units. I'll look at removing mapSvgAttributeToCSSProperty.
Eric Seidel (no email)
Comment 10
2009-12-17 11:27:06 PST
Thank you very much. Certainly not required that we remove mapSvgAttributeToCSSProperty, but if it's obvious to share code there, we might as well.
Marc-Antoine Ruel
Comment 11
2009-12-17 12:49:58 PST
Created
attachment 45102
[details]
Patch
WebKit Review Bot
Comment 12
2009-12-17 12:51:24 PST
style-queue ran check-webkit-style on
attachment 45102
[details]
without any errors.
Marc-Antoine Ruel
Comment 13
2009-12-17 12:52:07 PST
Created
attachment 45103
[details]
Patch
Marc-Antoine Ruel
Comment 14
2009-12-17 12:53:33 PST
- Removed the duplicate function. - Running try jobs (experimental):
http://build.chromium.org/buildbot/webkit-try/builders/Try%20Apple%20Leopard%20Intel%20Debug/builds/15
http://build.chromium.org/buildbot/webkit-try/builders/Try%20Apple%20Windows%20Debug/builds/14
Eric Seidel (no email)
Comment 15
2009-12-17 12:54:44 PST
Comment on
attachment 45103
[details]
Patch Yay! Thank you for the update ChangeLog. I think I would have just made it a protected static member of SVGStyledElement, the callsite in SVGFontFaceElement would not have had to change. But also think this is totally fine as a free function. r+
Eric Seidel (no email)
Comment 16
2009-12-17 13:11:31 PST
Comment on
attachment 45103
[details]
Patch Ah. I keep forgetting you're not a committer. cq+ too! :)
WebKit Commit Bot
Comment 17
2009-12-17 13:52:26 PST
Comment on
attachment 45103
[details]
Patch Clearing flags on attachment: 45103 Committed
r52288
: <
http://trac.webkit.org/changeset/52288
>
WebKit Commit Bot
Comment 18
2009-12-17 13:52:35 PST
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug