tree 00487a526e6e8275ca0f581c5a5f6c7ba65d53eb
parent 8883247a1e2004fd7ae6d91c8e3bcee03de1f797
author Ben Vanik <ben.vanik@gmail.com> 1677308137 -0800
committer Ben Vanik <ben.vanik@gmail.com> 1677900966 -0800

Adding requirement bits to bytecode modules and bumping version.
The compiler now emits per-module and per-function requirement bitfields
that indicate extensions needed to execute the bytecode they contain.
This allows for nice error messages on loading when the runtime has
certain extensions omitted:
```
D:\Dev\iree\runtime\src\iree\vm\bytecode\module.c:309: INVALID_ARGUMENT; required module features [EXT_F32] are not available in this runtime configuration; have [] while module requires [EXT_F32]; while invoking native function hal.executable.create; while calling import;
[ 1]   native hal.executable.create:0 -
[ 0] bytecode module.__init:446 D:\Dev\iree/tests/e2e/models/unidirectional_lstm.mlir:0:0
```

While making the breaking change I'm also adding a block_count field
to each function descriptor and a special block opcode that can be
used for verification and disassembly. All functions now have their
signatures embedded (not just exports) to allow for internal function
call verification.