riscv: fmax/fmin sNaN fix

DJ Delorie dj@redhat.com
Thu Feb 22 20:42:00 GMT 2018


"Carlos O'Donell" <carlos@redhat.com> writes:
> If there is a release out for RISC-V alrady, then this needs a bug number.

If that's the rule, then *every* change needs a bug number, because
there's always a "release out" for some platform...

(distinct from "backports to release branches need a bug number, for
tracking", if that's a rule)



More information about the Libc-alpha mailing list