RESOLVED FIXED 195255
Remove some more unused 32-bit code
https://bugs.webkit.org/show_bug.cgi?id=195255
Summary Remove some more unused 32-bit code
Tim Horton
Reported 2019-03-02 22:58:42 PST
Remove some more unused 32-bit code
Attachments
Patch (121.50 KB, patch)
2019-03-02 22:59 PST, Tim Horton
no flags
Archive of layout-test-results from ews103 for mac-highsierra (2.44 MB, application/zip)
2019-03-03 00:03 PST, EWS Watchlist
no flags
Archive of layout-test-results from ews107 for mac-highsierra-wk2 (2.51 MB, application/zip)
2019-03-03 00:15 PST, EWS Watchlist
no flags
Patch (123.23 KB, patch)
2019-03-03 00:35 PST, Tim Horton
no flags
Tim Horton
Comment 1 2019-03-02 22:59:04 PST Comment hidden (obsolete)
Tim Horton
Comment 2 2019-03-02 23:00:57 PST
Comment on attachment 363447 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=363447&action=review > Source/WebCore/page/CaptionUserPreferencesMediaAF.cpp:-472 > -#if defined(__LP64__) && __LP64__ I think this one needs to stay, if this code is built for Windows.
Darin Adler
Comment 3 2019-03-02 23:45:17 PST
Comment on attachment 363447 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=363447&action=review Seems super-unlikely it’s caused by this patch, but clearly the "using namespace WebCore" needs to be removed from Source/WebKit/Shared/Plugins/unix/PluginSearchPath.cpp, the file doesn’t use anything form WebCore. >> Source/WebCore/page/CaptionUserPreferencesMediaAF.cpp:-472 >> -#if defined(__LP64__) && __LP64__ > > I think this one needs to stay, if this code is built for Windows. Looks like the file is included in the Windows build, not sure about this particular line of code. > Source/WebCore/platform/graphics/cocoa/FontCascadeCocoa.mm:-54 > -#ifdef __LP64__ > #define URefCon void* > -#else > -#define URefCon UInt32 > -#endif There’s no use of URefCon so we can just delete this all. > Source/WebKit/Shared/mac/WebEventFactory.mm:360 > double force = 0; Should just define this below where it’s initialized.
EWS Watchlist
Comment 4 2019-03-03 00:03:13 PST Comment hidden (obsolete)
EWS Watchlist
Comment 5 2019-03-03 00:03:15 PST Comment hidden (obsolete)
EWS Watchlist
Comment 6 2019-03-03 00:15:31 PST Comment hidden (obsolete)
EWS Watchlist
Comment 7 2019-03-03 00:15:32 PST Comment hidden (obsolete)
Tim Horton
Comment 8 2019-03-03 00:35:04 PST
WebKit Commit Bot
Comment 9 2019-03-03 02:35:53 PST
Comment on attachment 363452 [details] Patch Clearing flags on attachment: 363452 Committed r242325: <https://trac.webkit.org/changeset/242325>
WebKit Commit Bot
Comment 10 2019-03-03 02:35:55 PST
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 11 2019-03-03 02:50:49 PST
mitz
Comment 12 2019-03-03 07:52:21 PST
Comment on attachment 363452 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=363452&action=review > Source/WebKit/Shared/API/Cocoa/WKFoundation.h:30 > #define WK_API_ENABLED 1 Is this useful anymore?
Darin Adler
Comment 13 2019-03-03 12:12:40 PST
Comment on attachment 363452 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=363452&action=review >> Source/WebKit/Shared/API/Cocoa/WKFoundation.h:30 >> #define WK_API_ENABLED 1 > > Is this useful anymore? I guess what you are asking is: Is it useful to be able to set WK_API_ENABLED to 0? If not, we can remove the 700+ references to it!
Tim Horton
Comment 14 2019-03-03 12:16:55 PST
No, it's not, but the patch was getting out of hand so I wanted to do that one separately :)
Tim Horton
Comment 15 2019-03-03 20:16:04 PST
(In reply to Tim Horton from comment #14) > No, it's not, but the patch was getting out of hand so I wanted to do that > one separately :) ... which was a good call, since the WK_API_ENABLED patch is 4x the size of this one: https://bugs.webkit.org/show_bug.cgi?id=195263
Note You need to log in before you can comment on or make changes to this bug.