On 5/4/24 8:41 AM, Jeff Law wrote:
The CI system caught a latent bug in the inline string comparison code
that shows up with rv32+zbb. It was hardcoding 64 when AFAICT it should
have been using BITS_PER_WORD.
So v2 with that fixed.
So per the discussion in today's call I reviewed a couple
The CI system caught a latent bug in the inline string comparison code
that shows up with rv32+zbb. It was hardcoding 64 when AFAICT it should
have been using BITS_PER_WORD.
So v2 with that fixed.
--
So with Chrstoph's patches from late 2022 we've had the ability to
inline strlen, and str[
