Re: [PATCH] v2: Implement range-op entry for sin/cos

2023-04-27 Thread Aldy Hernandez via Gcc-patches
On 4/27/23 13:53, Jakub Jelinek wrote: On Thu, Apr 27, 2023 at 01:46:19PM +0200, Aldy Hernandez wrote: On 4/27/23 13:13, Jakub Jelinek wrote: +unsigned bulps = targetm.libm_function_max_error (m_cfn, TYPE_MODE (type), + true); +if

Re: [PATCH] v2: Implement range-op entry for sin/cos

2023-04-27 Thread Jakub Jelinek via Gcc-patches
On Thu, Apr 27, 2023 at 01:46:19PM +0200, Aldy Hernandez wrote: > On 4/27/23 13:13, Jakub Jelinek wrote: > > > +unsigned bulps = targetm.libm_function_max_error (m_cfn, TYPE_MODE > > (type), > > + true); > > +if (bulps == ~0U) > > + r.s

Re: [PATCH] v2: Implement range-op entry for sin/cos

2023-04-27 Thread Aldy Hernandez via Gcc-patches
On 4/27/23 13:13, Jakub Jelinek wrote: +unsigned bulps = targetm.libm_function_max_error (m_cfn, TYPE_MODE (type), + true); +if (bulps == ~0U) + r.set_varying (type); +else if (bulps == 0) + r.set (type, dconstm1, dcons

[PATCH] v2: Implement range-op entry for sin/cos

2023-04-27 Thread Jakub Jelinek via Gcc-patches
Hi! On Tue, Apr 18, 2023 at 03:12:50PM +0200, Aldy Hernandez wrote: > [I don't know why I keep poking at floats. I must really like the pain. > Jakub, are you OK with this patch for trunk?] > > This is the range-op entry for sin/cos. It is meant to serve as an > example of what we can do for gl