[Libre-soc-isa] [Bug 1057] split out all int/fp min/max ops into their own RFC ls013

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=1057

Jacob Lifshay <programmerjake at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |IN_PROGRESS

--- Comment #3 from Jacob Lifshay <programmerjake at gmail.com> ---
filled out ls013:
https://git.libre-soc.org/?p=libreriscv.git;a=shortlog;h=70dda033b8caf1bcfcd53302b6e04481a5b8b787

commit 70dda033b8caf1bcfcd53302b6e04481a5b8b787
Author: Jacob Lifshay <programmerjake at gmail.com>
Date:   Fri Apr 14 18:47:16 2023 -0700

    add lkcl's justification for fmin/fmax

commit 763a74315adf9b265ce681f0ee6da24a176a08e7
Author: Jacob Lifshay <programmerjake at gmail.com>
Date:   Fri Apr 14 18:46:56 2023 -0700

    word wrap

commit 61d4047a5c4add0edb6068d6f26be2a0a2005bee
Author: Jacob Lifshay <programmerjake at gmail.com>
Date:   Fri Apr 14 18:42:09 2023 -0700

    fill out ls013 min/max fmin/fmax

(In reply to Luke Kenneth Casson Leighton from comment #2)
> (In reply to Jacob Lifshay from comment #1)
> > full list:
> > fminnum08(s)
> > fmaxnum08(s)
> 
> making me nervous the quantity, can we do the same trick
> of a mode-operand and get them down in quantity?
> the fp op table likely has the mode bits already.

I had to reorganize them somewhat...

> important justification, that using VSX may have
> different meaning (SVP64/VSX) so it is *really*
> crucial to have SVP64/SFFS ops.

added with a TODO(lkcl) so you can elaborate.

-- 
You are receiving this mail because:
You are on the CC list for the bug.