Adam

It looks like for `MRS` and `MSR`, the operand type should really be `ARM64_OP_REG_MRS` and `ARM64_OP_REG_MSR`, not `ARM64_OP_SYS`. I think the confusion arises from the "SYS" instruction (for which AT...

Looks like this may be a duplicate of #2213, but I'll leave this open as it's a somewhat more minimal example. I am also not sure this is strictly the...

Here's the complete matrix of build times from ddisasm's variants with different compilers: | Compiler | Arch | 2.3 | master | Change | | ------- | ------ | -------...

We've seen this internally as well where ddisasm and gtirb-pprinter versions were out of sync due to a recent breaking change. It looks like your builds are from the end...

This seems like a bug to me. Really, I'm not sure why we track `Type` as part of the `symbolic_operand` relation at all. Most consumers of `symbolic_operand` ignore it, and...

Generating byte-for-byte identical binaries after reassembly is not currently a design goal of ddisasm - instead it is to produce GTIRB IR and assembly that can be used to build...

I am having the same issue with using `env` in `jobs..container`, which the [Context Availability documentation](https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability) states should be available.

Hi @witbring, I am looking at resolving the remaining issues. I think I have a fix for the `date` binary, but I am trying to generate some additional smaller examples,...

The `true` binary should be fixed by [06fe6fa](https://github.com/GrammaTech/ddisasm/commit/06fe6fa1ce38007f38bb4697c304609482290b4d).

Hi @5c4lar thanks for your PR, and apologies for the delay in reviewing this and the related gtirb-pprinter and ddisasm PRs. One concern we have is that this is a...