Benjamin Bannier

As a payload for coverity to analyze we could pass it the sources of the runtime libraries, and an example JIT output exercising some of the functionality.

Since coverity requires not openly accessible wrapper tools, I am unsure how this can be implemented completely open. As an exploration, I added their tools to our ubuntu-20 Docker container....

mentioned in merge request !13

The first part of this is done: after linking all the modules together, we run a set of standard optimization passed on the joined module. Not sure if it's the...

The `-O3` gets into `runtime_cxx_flags_release` in `build/hilti/src/autogen/config.cc`, which is auto-generated by cmake. Need to get it out of there, and then re-add during JIT if optimization is requested.

To then add `-O3`, `ClangJIT::Implementation::compile()` can check `options().optimize`.

We currently allow both `--optimize` and `--debug` and it seems to make sense to support debugging optimized code as well. If we should want to support that we would need...

Let's just split the `-O3` out for now, and have ``--optimize`` put it back in. It's primarily to control that independently. We'll see if need to do more / something...

The tricky bit here seems to be that no matter what linker flags I try I still cannot remove as much information as `strip`. I am able to halve the...

There are a number of `file` analyzers in zeek/spicy-analyzers now ([PE](https://github.com/zeek/spicy-analyzers/blob/main/analyzer/pe/pe.evt), [PNG](https://github.com/zeek/spicy-analyzers/blob/main/analyzer/png/PNG.evt), [ZIP](https://github.com/zeek/spicy-analyzers/blob/main/analyzer/zip/zip.evt)), so I am closing this as done.