https://bugs.kde.org/show_bug.cgi?id=447991
Andreas Arnez changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=447991
--- Comment #6 from Jesus Checa ---
(In reply to Andreas Arnez from comment #3)
> Right, m3 == 0 is not a valid format code. The z/Architecture Principle of
> Operation states:
>
> The M3 field specifies the floating-point format. The floating-poin
https://bugs.kde.org/show_bug.cgi?id=447991
--- Comment #5 from Andreas Arnez ---
(In reply to Mark Wielaard from comment #4)
> OK, but does that mean that "vflr" isn't a real opcode because it doesn't
> define on what format it operates?
Basically yes. Well, strictly speaking, the opcode only c
https://bugs.kde.org/show_bug.cgi?id=447991
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=447991
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=447991
--- Comment #3 from Andreas Arnez ---
(In reply to Jesus Checa from comment #2)
> ...
> Checking s390x opcodes, it feels like s390_irgen_VFLR is missing the case
> for when m3 == 0 (provided my inline asm is right).
Right, m3 == 0 is not a valid format
https://bugs.kde.org/show_bug.cgi?id=447991
Jesus Checa changed:
What|Removed |Added
CC||jch...@redhat.com
--- Comment #2 from Jesus Checa
https://bugs.kde.org/show_bug.cgi?id=447991
--- Comment #1 from Andreas Arnez ---
Created attachment 145141
--> https://bugs.kde.org/attachment.cgi?id=145141&action=edit
Fix VFLRX instruction
The problem was due to a typo in s390_irgen_VFLR. This fixes the typo.
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=447991
Andreas Arnez changed:
What|Removed |Added
Assignee|jsew...@acm.org |ar...@linux.ibm.com
--
You are receiving this
