Jungshik Shin 831bc23303 Intl.DateTimeFormat: throw RangeError for non-finite input ... intl.js throws an exception when datetime-value to format is Infinity or NaN, but there was a way to thwart the check. Moreover, intl.js and runtime-intl.cc have unnecessary conversions of 'Number->Date->Number'. I removed the unnecessary conversion and made 'Number' be passed to %InternalDateFormat. With this streamlining, the work-around mentioned above does not work anymore. Add a check in runtime_intl.cc for Infinity/NaN and throw a RangeError. Add invalid-time test for invalid datetime-values passed to Intl.DateTimeFormat.format(). Bug: chromium:774833 Test: intl/date-format/invalid-time.js Cq-Include-Trybots: master.tryserver.v8:v8_linux_noi18n_rel_ng Change-Id: Idc575e532a86ee110dc4bb945ae023d6516650ee Reviewed-on: https://chromium-review.googlesource.com/724860 Commit-Queue: Jungshik Shin <jshin@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#48765}		2017-10-19 23:25:52 +00:00
..
break-iterator
collator
date-format	Intl.DateTimeFormat: throw RangeError for non-finite input	2017-10-19 23:25:52 +00:00
general	Correct the misuse of uloc_{to,from}LanguageTag	2017-10-12 06:33:35 +00:00
number-format	NumberFormat: default mnsd value is 1	2017-02-14 17:12:49 +00:00
overrides
string
assert.js	[intl] Add new semantics + compat fallback to Intl constructor	2016-12-23 14:32:16 +00:00
bad-target.js	[intl] Remove redundant type checking system	2017-01-09 22:24:57 +00:00
intl.gyp
intl.isolate
intl.status	resolvedTimezone for Etc/UTC should be UTC per Ecma 402	2017-05-04 21:17:39 +00:00
not-constructors.js	[intl] Remove new.target check in Intl functions and method	2016-12-20 16:06:19 +00:00
OWNERS	Add COMPONENT tags to OWNERS files where appropriate	2017-05-22 10:15:28 +00:00
regexp-assert.js
regexp-prepare.js
regress-4870.js
regress-5179.js
testcfg.py
toStringTag.js	[intl] Create the Intl constructors to C++	2016-12-27 17:10:00 +00:00
utils.js