You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
linux/ppc64le
linux/ppc64
What did you do?
CL160429 uncovered a bug in the assembler, where bit 31 of XX1-form instructions is flipped when using extended mnemonics (FP/VMX registers as arguments, instead of VSX).
What did you expect to see?
F0-F31 must map into VS0-VS13 and V0-V31 must map into VS32-VS63.
What did you see instead?
The problem makes FP register arguments become VMX registers (or, in VSX terms, VS0-VS31 into VS32-VS63). This doesn't cause an illegal instruction, but may cause register clobbering.
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
CL160429 uncovered a bug in the assembler, where bit 31 of XX1-form instructions is flipped when using extended mnemonics (FP/VMX registers as arguments, instead of VSX).
What did you expect to see?
F0-F31 must map into VS0-VS13 and V0-V31 must map into VS32-VS63.
What did you see instead?
The problem makes FP register arguments become VMX registers (or, in VSX terms, VS0-VS31 into VS32-VS63). This doesn't cause an illegal instruction, but may cause register clobbering.
The text was updated successfully, but these errors were encountered: