[llvm-branch-commits] [clang] [llvm] release/18.x: [RISCV] Re-separate unaligned scalar and vector memory features in the backend. (PR #92143)

[Craig Topper via llvm-branch-commits]

topperc wrote:

> I don't think we need to backport this at all. None of the in tree cpus fall into the category where the distinction is important, and I don't feel we have any obligation to backport support for our of tree forks.

There's no out of tree fork involved here. The bug reporter was using stock LLVM to compile for the Kendryte K230 board. A developer from the RISE System Libraries group reported this same issue in a presentation yesterday. It is impacting their work on chromium zlib on the same K230 board. zlib does scalar unaligned accesses.

https://github.com/llvm/llvm-project/pull/92143