Scott Linder

Agreed, writing a tool to convert to/from vim docs and something like [Pandoc](http://johnmacfarlane.net/pandoc/) (which then opens up the floor for using pre-existing tools to get any document format imaginable, markdown...

The layouts are specified at https://llvm.org/docs/AMDGPUUsage.html#code-object-metadata Comgr doesn't provide any abstraction over the multiple formats; the consumer has to implement each in order to support both V2 and V3 code...

As an update on this, the first step will be to define the MT safety of all non-trivially-MT-safe APIs in Comgr to be MT-unsafe. Then future work to give APIs...

Are the actions you mention the only ones performed? The `AMD_COMGR_ACTION_ASSEMBLE_SOURCE_TO_RELOCATABLE` action operates on ISA-level assembly text (e.g. .S files) not on LLVM IR/BC. This is related to #7; "source"...

Currently no, there are no actions which accept LLVM IR. An action to convert LLVM IR to BC could be added if it is useful.

This is a known bug in the loader which we are working on. You can workaround it by passing "-mno-code-object-v3" in the option string during compilation. We hope to have...

I believe the common thread in all of the APIs is that `AMD_COMGR_STATUS_ERROR_INVALID_ARGUMENT` indicates an error on the caller's part, whether it be an invalid action kind, invalid language, etc....

Do you have a minimal example? Currently the only output comes from tools which do not expose options to control when output is flushed, but as part of #2 we...