[Bug target/117573] RISC-V target -O2 generates Misaligned Access despite -mstrict-align

[tarik.ibrahimovic--- via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117573

--- Comment #6 from Tarik Ibrahimović <tarik.ibrahimo...@chili-chips.xyz> ---
Does "corrupted" mean it got mixed up somewhere in the compiling process? I
emphasize once again, that the generated code does not cause any misalignments
when -O0 is used. 

One more thing which may be of importance is that CPU implementations which
ignore the overflowing part of the misaligned memory access execute the code
correctly.