For table driven algorithms with --table-idx-width greater than 1, it would be nice to generate code that ensures aligned access.
Currently, any trailing unaligned bytes are handled individually (i.e. anything after the Remaining bytes with the standard algorithm comment), but it would be great to handle leading unaligned bytes individually as well, to ensure that the main loop is using aligned loads.
Thanks for pycrc!
For table driven algorithms with
--table-idx-width
greater than 1, it would be nice to generate code that ensures aligned access.Currently, any trailing unaligned bytes are handled individually (i.e. anything after the
Remaining bytes with the standard algorithm
comment), but it would be great to handle leading unaligned bytes individually as well, to ensure that the main loop is using aligned loads.