// Exception message for invalid typed arrays different between x64/ia32. Repro:

try {
  new Uint32Array(new ArrayBuffer(), 4294967295, 1073741824);
} catch (e) {
  print(e.message);
}

# Compared x64,ignition with ia32,ignition
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1234 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
# Flags of ia32,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1234 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
#
# Difference:
- start offset of Uint32Array should be a multiple of 4
+ Invalid typed array length
#
### Start of configuration x64,ignition:
start offset of Uint32Array should be a multiple of 4

### End of configuration x64,ignition
#
### Start of configuration ia32,ignition:
Invalid typed array length

### End of configuration ia32,ignition

// Simpler repro. Here the exception is only raised in the ia32 case:

new Uint8Array(1073741824);

// Output:

# Compared x64,ignition with ia32,ignition
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1234 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
# Flags of ia32,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 1234 --ignition --turbo-filter=~ --hydrogen-filter=~ --validate-asm --nocrankshaft
#
# Difference:
+ /usr/local/google/home/machenbach/v8/v8/repro.js:2: RangeError: Invalid typed array length
#
### Start of configuration x64,ignition:

### End of configuration x64,ignition
#
### Start of configuration ia32,ignition:
/usr/local/google/home/machenbach/v8/v8/repro.js:2: RangeError: Invalid typed array length
new Uint8Array(1073741824);
^



### End of configuration ia32,ignition

@Yang: Is this just a case of RangeError suppression that we need? I.e. is this a dupe of  issue 664068 ?

 Issue 689325  has been merged into this issue.

 Issue 689346  has been merged into this issue.

CL to mock things out: https://chromium-review.googlesource.com/c/439164/

 Issue 689360  has been merged into this issue.

 Issue 688816  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/851d2001fc6a6947054514999908e34bcb50a215

commit 851d2001fc6a6947054514999908e34bcb50a215
Author: Michael Achenbach <machenbach@chromium.org>
Date: Thu Feb 09 08:33:16 2017

[foozzie] Mock out large typed arrays

BUG= chromium:688856 , chromium:664068 
NOTRY=true

Change-Id: Icf0e7a51693b6d399c8395eb0bbed9a3c373eb0a
Reviewed-on: https://chromium-review.googlesource.com/439164
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#43052}
[modify] https://crrev.com/851d2001fc6a6947054514999908e34bcb50a215/tools/foozzie/BUILD.gn
[modify] https://crrev.com/851d2001fc6a6947054514999908e34bcb50a215/tools/foozzie/v8_foozzie.py
[modify] https://crrev.com/851d2001fc6a6947054514999908e34bcb50a215/tools/foozzie/v8_mock.js
[add] https://crrev.com/851d2001fc6a6947054514999908e34bcb50a215/tools/foozzie/v8_mock_archs.js
[modify] https://crrev.com/851d2001fc6a6947054514999908e34bcb50a215/tools/foozzie/v8_suppressions.py

ClusterFuzz testcase 4777512011038720 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

ClusterFuzz has detected this issue as fixed in range 43228:43229.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4770298613465088

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_turbo_x64_ia32
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition_turbo:ia32,ignition_turbo
  sources: d70
  
Sanitizer: address (ASAN)

Fixed: V8: 43228:43229

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97k7RTwhOvHEIUkVIu0Q4fxXwgBkP8J2ijhrRIP0AoMc2XUSAVrZuNUqRwWQBpQ3Z4mram1LfAIFwuPNq93pY4KSzSeYrJbME5FWkM_2XoIJSpNSyoDfOI65PpHHMb1d-_qLL_V_PWqPD2c8-YFrD2MNWdHyUWWPhUpi4POiQ96IE-QGjFR9fVFEp12nAy6mucycgDl_YDg1ChP2mPIU_KUkmy3gj-KfZ5R2rCkLpr9nBdrby6n29gEYry-luX-5iOhD5PK0wwuRYKYqzJJZQStCYl8SWnyQVjmTNIgklMt8Dft9YvttF7YmmlwEAC8QjSlnezYU378_3QXjnsHV1xtkduFxwNGjxzAleqfcb5BSTvj5WHsCgh2jkEo-KDUJgpyZIpOOCwS00MngwdsHPsyRuQ_Wg?testcase_id=4770298613465088


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.