commit 303f865bbaafed4b73532987a6eb8f8bbab1590f
author Kojo Acquah <KoolJBlack@users.noreply.github.com> Tue Jun 15 12:46:54 2021 -0700
committer GitHub <noreply@github.com> Tue Jun 15 12:46:54 2021 -0700
tree d8260aaa114ee18b2f5b3a81e9c0df6d846eb7b9
parent aa7409fc0b48b2e3d1bd36795e4bcdb05a3c4568

IREE Static Library Loader Compiler Integration (#5950)

Compiler integration for static library building:

- Compiler integration for generating static libraries and header files
- Fixed pointer references in `static_library_loader.c`

### Compiler Integration

New flag: `--iree-llvm-static-library-output-path` specifies the location for the static library. 2 files are saved to this path: '.o' static object and generated header file. When a static library path is defined, the library name for the static loader is embedded into the executable instead of a dynamic library contents. The '.vmfb' output target is still specified with `-o` flag. 

Example static library generation: 
```
 bazel run :iree-translate -- \
         /path/to/mlir/simple_embedding.mlir \
        -iree-mlir-to-vm-bytecode-module \
        -iree-hal-target-backends=dylib-llvm-aot \
        -o /path/to/library/static.vmfb \
        --iree-llvm-static-library-output-path=/path/to/library/static.o 
```

Static libraries are generated and linked on Linux using the `dylib-llvm-aot` backend. Other platforms and targets triples may need further validation.

Addresses issue #5666