The compiler option 'deterministic' was only recognized when given
as an option to the compiler, not when it was specified in a
-compile() attribute in the source file.

https://bugs.erlang.org/browse/ERL-498

Also test other options that turns off certain optimizations or
instruction sets.

The new chunk stores atoms encoded in UTF-8.

beam_lib has also been modified to handle the new
'utf8_atoms' attribute while the 'atoms' attribute
may be a missing chunk from now on.

The binary_to_atom/2 BIF can now encode any utf8
binary with up to 255 characters.

The list_to_atom/1 BIF can now accept codepoints
higher than 255 with up to 255 characters (thanks
to Björn Gustavsson).

missing_testheap/1 is no longer relevant for the following reasons:

1) Because of the literal pool introduced in R12, no test_heap
   instructions are needed in the guards.

2) beam_validator would abort the compilation if any needed test_heap
   instructions were missing.

The two bad record usage test cases in compile_SUITE do not
belong there, as the errors are detected in erl_lint. Move the
test to the erl_lint_SUITE.

Cover more code in v3_core.

Since both the STDLIB and compiler applications turn warnings
into errors, we must stop using the old deprecated crypto functions.

While we are at it, generalize the format of the key tuple returned
by beam_lib:make_crypto_key/2 to facilitate introducing new crypto
methods in the future. Change the format to:

  {Type,Key,IV,BlockSize}

where Type, Key, and IV are the first three arguments for either
crypto:block_encrypt4/ or crypto:block_decrypt/4, and BlockSize
is the block size for the crypto algorithm (it is needed to properly
pad the plaintext blocks before encryption).