transpile: tests: add out_of_range_int.c test

[kkysen]

A test for #1435. It was broken by #1266 (specifically, 7eaa39f, which also doesn't compile). It seems we're not handling the U suffix, which requires a temporary cast to c_uint before getting coerced to int32_t/i32.

4a4c0cc is the current snapshot, while 36d829e is what it was before #1266, which still compiles.

[fw-immunant]

Ah, my bad re: 7eaa39f not compiling--it depends on 67e6eeb but got reordered prior to it during cleanup of that PR.

I believe the problem here is referenced by the doc comment for literal_kind_matches_ty:

Return whether the literal can be directly translated as this type. This does not check that the literal fits into the type's range of values (as doing so is in general dependent on the target platform), just that it is the appropriate kind for the type.

For fixed-size types like int32_t, we can relatively easily check the literal against their fixed bounds, but for types like libc::c_int we need to be able to determine the bounds for int on the target platform.

[kkysen]

for types like libc::c_int we need to be able to determine the bounds for int on the target platform.

See #1442 now, but I chose to use the narrowest bound for platform-dependent types like int so that the resulting code works on all platforms.

[kkysen]

• Superseded by transpile: fix out-of-range integers #1442.