hwtypes
hwtypes copied to clipboard
Python implementations of fixed size hardware types (Bit, BitVector, UInt, SInt, ...) based on the SMT-LIB2 semantics
For a newcomer the APIs are not obvious even from the unit tests.
This is a minor thought, but a case came up where I wanted to use the `adc` operation but only need the carry out (not the carry in). I can...
Not sure if this is something we want to support, since a workaround is to just call `int` on the BV index value (but then maybe we should add an...
In defining instruction sets and extension it would be convenient if the following worked: ```Python class Base(Enum): a = 0 b = 1 class Extension(Base): c = 2 class Other(Enum):...
Add an array type to better match the magma type hierarchy.
Currently the typing of `ite` is a mess and inconsistent with magma. Now before you all go looking at the mess I want you all to consider the following code...
There have been and continue to be a number of areas of where `[SMT]BitVector` and `Bits` have diverged on the typing of methods and operators. I propose building a unified...
After seeing the request for AnonomousProduct, this got me thinking about #71 and I wanted to give a systematic description of what types we currently have to track naming inconsistencies....
Currently, Magma has a different Enum/Product/Tuple from the hwtypes.adt types. This causes a lot of hacked user code in order to get Peak to compile to magma. I would request...