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

[Alex Bradbury via llvm-branch-commits]

asb wrote:

My thoughts:
* Thanks to @negge and others for clarifying who this is affecting and how
* It's very unfortunate we've broken some use cases here. Though as, by my understand, this is affecting people using internal flags as opposed to documented top-level flags I feel there's not a _strong_ obligation to fix the issue in a point release.
* That said, if we can fix it with minimal risk of introducing more problems then it would be nice to do so as long as the release managers are happy
* I think the solution of keeping fast-unaligned-access and adding +unaligned-scalar-mem is pragmatic
* Patch LGTM.

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