> On Aug 29, 2022, at 1:07 PM, Jeff Law via Gcc-patches > <gcc-patches@gcc.gnu.org> wrote: > > ... > I guess we could do specialization based on the input range. So rather than > calling "sin" we could call a special one that didn't have the reduction step > when we know the input value is in a sensible range. There's some precedent for that, though for a somewhat different reason: functions like "log1p". And in fact, it would make sense for the optimizer to transform log calls into log1p calls when the range is known to be right for doing so. paul
Re: [PATCH] [ranger] x == -0.0 does not mean we can replace x with -0.0
Koning, Paul via Gcc-patches Mon, 29 Aug 2022 10:37:43 -0700
- [PATCH] [ranger] x == -0.0 does not mean we... Aldy Hernandez via Gcc-patches
- Re: [PATCH] [ranger] x == -0.0 does no... Jakub Jelinek via Gcc-patches
- Re: [PATCH] [ranger] x == -0.0 doe... Aldy Hernandez via Gcc-patches
- Re: [PATCH] [ranger] x == -0.0... Jakub Jelinek via Gcc-patches
- Re: [PATCH] [ranger] x == ... Aldy Hernandez via Gcc-patches
- Re: [PATCH] [ranger] ... Jeff Law via Gcc-patches
- Re: [PATCH] [rang... Aldy Hernandez via Gcc-patches
- Re: [PATCH] [... Jeff Law via Gcc-patches
- Re: [PATCH] [... Toon Moene
- Re: [PATCH] [... Jeff Law via Gcc-patches
- Re: [PATCH] [... Koning, Paul via Gcc-patches
- Re: [PATCH] [... Toon Moene
- Re: [PATCH] [... Aldy Hernandez via Gcc-patches
- Re: [PATCH] [ranger] x == ... Aldy Hernandez via Gcc-patches