Simon Zünd 82f6179c63 [array] Prevent negative work array capacity when sorting ... When allocating large arrays on 32-bit systems, the length conversion caused the work array capacity to become negative. As the sort range is currently clamped at kSmiMaxValue anyway, the fix is to also clamp the work capacity to that value. R=jgruber@chromium.org Bug: chromium:967065 Change-Id: I9ea60464c5b7f3796c5389cbaf668b990eddecf6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1630672 Auto-Submit: Simon Zünd <szuend@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#61845}		2019-05-27 10:41:44 +00:00
..
binutils	Python3 compatibility: use open() instead of file()	2019-04-05 16:22:20 +00:00
colorama	Add colorama package to DEPS so that pylib can import it	2017-10-24 14:18:49 +00:00
googletest	Update V8 DEPS.	2019-01-22 14:49:04 +00:00
inspector_protocol	[DevTools] Roll inspector-protocol to v8	2019-05-22 06:15:38 +00:00
v8/builtins	[array] Prevent negative work array capacity when sorting	2019-05-27 10:41:44 +00:00
wasm-api	[wasm-c-api] Add upstream examples as tests	2019-04-17 18:04:16 +00:00