| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
... this makes the doc test not exist under nostd, yes. `VecSink` does
not have a no-std alternative that makes the example reasonable.
|
|
|
|
it was built in-place around yaxpeax-x86, hoisted out once it seemed
suitable and could be generalized. yay!
also include a Makefile in yaxpeax-arch now to test that various crate
feature flag combinations.. work.
|
|
|
|
also bump rust-toolchain and edition of yaxpeax-arch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
also update yaxpeax-arch to 0.2.4
|
|
|
|
also revise an `unsafe` that might be unsafe un extremely unlikely
circumstances - no one should be passing yaxpeax a `&[u8]` larger than
`isize::MAX`, but on 32-bit architectures we can't necessarily guarantee
that it won't happen
|
|
|
|
|
|
the previous test and code only tested one concrete archtecture, and it
turns out never required `std::error::Error` on `DecodeError`.
|
