On 6/6/25 4:14 AM, Stafford Horne wrote:
Hello,
This seems to be causing a build regression on the or1k port.
I have not quite figured it out yet but I have bisected to this commit.
The failure is as below, this seems to be caused by the cstoresi4 instruction
produced by
or1k.md. So I think its likely something we are doing funny in the port.
Thanks to Jeff for pointing this out. If you have any idea let me know.
THat would be an indicator of a target issue. I wouldn't be totally
surprised if the additional checking is changing whether or not some
transformation is allowed and thus sending the or1k port down a
different path.
Jeff
