Modernize.
Created attachment 249943 [details] patch
Comment on attachment 249943 [details] patch r=me
Created attachment 249970 [details] non-llvm build fixes
Created attachment 249972 [details] another
Created attachment 249975 [details] another
Created attachment 249977 [details] another
Created attachment 249979 [details] another
https://trac.webkit.org/r182271
This broke four JSC tests on Windows: ** The following JSC stress test failures have been introduced: mozilla-tests.yaml/ecma/Date/15.9.5.8.js.mozilla mozilla-tests.yaml/ecma/Date/15.9.5.8.js.mozilla-baseline mozilla-tests.yaml/ecma/Date/15.9.5.8.js.mozilla-dfg-eager-no-cjit-validate-phases mozilla-tests.yaml/ecma/Date/15.9.5.8.js.mozilla-llint Can you fix, or should I roll this out?
I don't understand how. This patch didn't touch anything on JSC level or below.
(In reply to comment #10) > I don't understand how. This patch didn't touch anything on JSC level or > below. It might just be the bot. I'm noticing that one of the two bots is green, while the other is failing.
This patch touched WebCore, WebKit and WebKit2 only. Literally no code affected here should end up in jsc.exe.
Comment on attachment 249979 [details] another View in context: https://bugs.webkit.org/attachment.cgi?id=249979&action=review > Source/WebCore/platform/network/CacheValidation.cpp:113 > + auto maxAge = response.cacheControlMaxAge(); > + if (maxAge) Can fold this into the if condition. > Source/WebCore/platform/network/HTTPParsers.cpp:243 > + // This assumes system_clock epoch equals Unix epoch which is true for all implementations but unspecified. > + // FIXME: The parsing function should be switched to std::chrono too. Maybe we can use std::chrono::system:clock::to_time_t or something?