https://bugs.kde.org/show_bug.cgi?id=484426
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=484426
--- Comment #7 from Paul Floyd ---
(In reply to Mark Wielaard from comment #6)
> This looks good to me. But I have not tested it. And I have to trust you on
> the emit code (too lazy to look up the instr enc)
>
> It looks like
https://bugs.kde.org/show_bug.cgi?id=484426
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #6 from Mark
https://bugs.kde.org/show_bug.cgi?id=484426
--- Comment #5 from Paul Floyd ---
The patch doesn't cover the vector versions.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484426
--- Comment #4 from Paul Floyd ---
Created attachment 167836
--> https://bugs.kde.org/attachment.cgi?id=167836=edit
Patch adding new Iops
Dunno why arm64 didn't add more FPCR rounding modes. Probably because of
historical baggage from am32 where a)
https://bugs.kde.org/show_bug.cgi?id=484426
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=484426
--- Comment #3 from Paul Floyd ---
I think that I understand the problem. arm64 has two overlapping ways of doing
floating point rounding.
The mnemonics are FRINT (Float Round to Int) and then one more letter for the
kind of rounding.
The FPCR
https://bugs.kde.org/show_bug.cgi?id=484426
--- Comment #2 from Paul Floyd ---
Comment from code:
* FRINTA, FRINTN are kludged .. they just round to nearest. No special
handling for the "ties" case. FRINTX might be dubious too.
* Ditto FCVTXN. No idea what "round to odd" means.
https://bugs.kde.org/show_bug.cgi?id=484426
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
