Default gcAllowVeryLargeObjects to true (dotnet/coreclr#8853)
authormikedn <onemihaid@hotmail.com>
Tue, 10 Jan 2017 05:00:39 +0000 (07:00 +0200)
committerJan Kotas <jkotas@microsoft.com>
Tue, 10 Jan 2017 05:00:39 +0000 (21:00 -0800)
commit8176f8b4935e74ba1f4fada3768f962229f61af3
tree8ccc86f5e2f47ba714b94f1d2cec640af038a094
parent899a596992d5e290862155142cdd0c90c8536fd9
Default gcAllowVeryLargeObjects to true (dotnet/coreclr#8853)

* Default gcAllowVeryLargeObjects to true

* Update tests for gcAllowVeryLargeObjects

These 2 tests appear to rely on gcAllowVeryLargeObjects being false in that they expect an exception to be thrown when allocating a very large array.

Increase the number of array elements so that an OutOfMemoryException is always thown no matter what value gcAllowVeryLargeObjects has. 81*98*58*36*74*4 is 4906065024 which is larger than 2^32, the theoretical array length limit.

Commit migrated from https://github.com/dotnet/coreclr/commit/163983ecf59c70d7c286e740f7cd3230f12a0f3c
src/coreclr/src/inc/clrconfigvalues.h
src/coreclr/tests/src/JIT/Regression/VS-ia64-JIT/V2.0-RTM/b539509/b539509.cs
src/coreclr/tests/src/JIT/jit64/regress/vsw/539509/test1.cs