Original review https://codereview.chromium.org/25855005.
authorcira@chromium.org <cira@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 11 Oct 2013 17:54:31 +0000 (17:54 +0000)
committercira@chromium.org <cira@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Fri, 11 Oct 2013 17:54:31 +0000 (17:54 +0000)
commitc0ff0b284ddb02f5477abfa52cbb3d0075b34053
tree207febe847b96d0f30766ae44d7ed443affcea00
parentf55fc759dc691dc97b2ef227947f8e4ecb6565e7
Original review https://codereview.chromium.org/25855005.

Reverting reverted r17148 and fixing build (test) breakage by side stepping the Windows vs. Linux issue of different Date object for the same millisecond time stamp.
We do that by using UTC Date methods (they eliminate DST problems).

Windows:
new Date(129193200000);
Sun Feb 03 1974 23:00:00 GMT-0800 (Pacific Standard Time)

Linux:
new Date(129193200000);
Mon Feb 04 1974 00:00:00 GMT-0700 (PST)

BUG=2919
R=dslomov@chromium.org, mnita@google.com

Review URL: https://codereview.chromium.org/26918002

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@17171 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/i18n.js
test/intl/date-format/parse-MMMdy.js
test/intl/date-format/parse-mdy.js
test/intl/date-format/parse-mdyhms.js
test/intl/date-format/timezone-name.js [moved from test/intl/date-format/utils.js with 66% similarity]
test/intl/testcfg.py