WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
182753
[Tools] --wincairo should imply --64-bit by default.
https://bugs.webkit.org/show_bug.cgi?id=182753
Summary
[Tools] --wincairo should imply --64-bit by default.
Ross Kirsling
Reported
2018-02-13 16:32:28 PST
[Tools] --wincairo should imply --64-bit by default.
Attachments
Patch
(3.43 KB, patch)
2018-02-13 16:33 PST
,
Ross Kirsling
no flags
Details
Formatted Diff
Diff
Patch
(4.89 KB, patch)
2018-02-13 16:57 PST
,
Ross Kirsling
no flags
Details
Formatted Diff
Diff
Patch for landing
(5.01 KB, patch)
2018-02-14 11:43 PST
,
Ross Kirsling
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Ross Kirsling
Comment 1
2018-02-13 16:33:22 PST
Created
attachment 333743
[details]
Patch
Ross Kirsling
Comment 2
2018-02-13 16:57:37 PST
Created
attachment 333749
[details]
Patch
Daniel Bates
Comment 3
2018-02-13 21:45:51 PST
Comment on
attachment 333749
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=333749&action=review
> Tools/ChangeLog:3 > + [Tools] --wincairo should imply --64-bit by default.
Shouldn’t the tools query the architecture by default? I mean, the WinCairo 64 Bit Release builder does not explicitly pass —64-bit (*) to build-webkit and it builds for 64-bit. I take it from the existence of this patch that the default build architecture of the bot was modified by running script webkit-configuration. (*) <
https://build.webkit.org/builders/WinCairo%2064-Bit%20Release/builds/10929/steps/compile-webkit/logs/stdio
>
> Tools/Scripts/webkitdirs.pm:145 > +my $isExplicit32Bit;
Maybe a better name for this would be willBuildFor32Bit or willBuildFor32BitArchitecture and similarly rename the functions below.
> Tools/Scripts/webkitdirs.pm:1258 > + $isWin64 = checkForArgumentAndRemoveFromARGV("--64-bit") || (isWinCairo() && !isExplicit32Bit());
The parentheses are not necessary by operator precedence [1]. [1] <
https://perldoc.perl.org/perlop.html#Operator-Precedence-and-Associativity
>
Daniel Bates
Comment 4
2018-02-13 21:48:45 PST
(In reply to Daniel Bates from
comment #3
)
> Comment on
attachment 333749
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=333749&action=review
> > > Tools/ChangeLog:3 > > + [Tools] --wincairo should imply --64-bit by default. > > Shouldn’t the tools query the architecture by default? I mean, the WinCairo > 64 Bit Release builder does not explicitly pass —64-bit (*) to build-webkit > and it builds for 64-bit. I take it from the existence of this patch that > the default build architecture of the bot was modified by running script > webkit-configuration. >
*set-webkit-configuration
Ross Kirsling
Comment 5
2018-02-14 11:12:44 PST
(In reply to Daniel Bates from
comment #3
)
> Comment on
attachment 333749
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=333749&action=review
> > > Tools/ChangeLog:3 > > + [Tools] --wincairo should imply --64-bit by default. > > Shouldn’t the tools query the architecture by default? I mean, the WinCairo > 64 Bit Release builder does not explicitly pass —64-bit (*) to build-webkit > and it builds for 64-bit. I take it from the existence of this patch that > the default build architecture of the bot was modified by running script > webkit-configuration. > > (*) > <
https://build.webkit.org/builders/WinCairo%2064-Bit%20Release/builds/10929/
> steps/compile-webkit/logs/stdio>
Thanks for pointing this out! Experimenting locally, it seems that it's not about `set-webkit-configuration`, but rather that x64 is correctly identified when compiling with Ninja. It's when `--no-ninja` is specified that the script checks `isWin64()`:
https://github.com/WebKit/webkit/blob/master/Tools/Scripts/webkitdirs.pm#L2138-L2148
So fixing the definition of `isWin64()` is still worthwhile, but the reason is slightly more specific than I realized.
> > Tools/Scripts/webkitdirs.pm:1258 > > + $isWin64 = checkForArgumentAndRemoveFromARGV("--64-bit") || (isWinCairo() && !isExplicit32Bit()); > > The parentheses are not necessary by operator precedence [1]. > > [1] > <
https://perldoc.perl.org/perlop.html#Operator-Precedence-and-Associativity
>
Whoops, thought this was a style guide requirement.
Ross Kirsling
Comment 6
2018-02-14 11:43:58 PST
Created
attachment 333825
[details]
Patch for landing
WebKit Commit Bot
Comment 7
2018-02-14 12:31:21 PST
The commit-queue encountered the following flaky tests while processing
attachment 333825
[details]
: imported/w3c/web-platform-tests/WebCryptoAPI/sign_verify/rsa_pkcs.worker.html
bug 182803
(author:
jiewen_tan@apple.com
) The commit-queue is continuing to process your patch.
WebKit Commit Bot
Comment 8
2018-02-14 12:31:55 PST
Comment on
attachment 333825
[details]
Patch for landing Clearing flags on attachment: 333825 Committed
r228480
: <
https://trac.webkit.org/changeset/228480
>
WebKit Commit Bot
Comment 9
2018-02-14 12:31:57 PST
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 10
2018-02-14 12:32:53 PST
<
rdar://problem/37544518
>
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