While investigating "LibraryCallKit::generate_string_range_check" for integer overflow we noticed that there doesn't seem to be any test exercizing count values close to max int (and min int).
As the intrinsic doesn't add any range check, we should add (randomized or fuzzing) tests to check that calls to connected StringLatin1 and StringUTF16 methods don't unexpectedly cause any overflow (in particular with the LShift node added by generate_string_range_check).