From: Aldy Hernandez <aldyh@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [COMMITTED] Add cases for CFN_BUILT_IN_SIGNBIT[FL].
Date: Fri, 14 Oct 2022 16:23:15 +0200 [thread overview]
Message-ID: <CAGm3qMXQC9p6LEHYeKWDWgCA_G17dba8vfMDQE_0jhYvmb3Mew@mail.gmail.com> (raw)
In-Reply-To: <Y0k3F4kbgEdwyev2@tucnak>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
Done.
Thanks.
Aldy
On Fri, Oct 14, 2022 at 12:17 PM Jakub Jelinek <jakub@redhat.com> wrote:
>
> On Fri, Oct 14, 2022 at 12:03:16PM +0200, Aldy Hernandez via Gcc-patches wrote:
> > gcc/ChangeLog:
> >
> > * gimple-range-op.cc
> > (gimple_range_op_handler::maybe_builtin_call): Add
> > CFN_BUILT_IN_SIGNBIT[FL]* entries.
> > ---
> > gcc/gimple-range-op.cc | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/gcc/gimple-range-op.cc b/gcc/gimple-range-op.cc
> > index bc4389eb2e1..9bdef3d45c0 100644
> > --- a/gcc/gimple-range-op.cc
> > +++ b/gcc/gimple-range-op.cc
> > @@ -757,6 +757,8 @@ gimple_range_op_handler::maybe_builtin_call ()
> > break;
> >
> > case CFN_BUILT_IN_SIGNBIT:
> > + case CFN_BUILT_IN_SIGNBITF:
> > + case CFN_BUILT_IN_SIGNBITL:
>
> CASE_FLT_FN (CFN_BUILT_IN_SIGNBIT):
> instead of the above 3?
>
> Jakub
>
[-- Attachment #2: 0003-Replace-CFN_BUILTIN_SIGNBIT-cases-with-CASE_FLT_FN.patch --]
[-- Type: text/x-patch, Size: 955 bytes --]
From f44a0f5530012e2a0108e9034c7d63adcd21d7ff Mon Sep 17 00:00:00 2001
From: Aldy Hernandez <aldyh@redhat.com>
Date: Fri, 14 Oct 2022 15:02:06 +0200
Subject: [PATCH] Replace CFN_BUILTIN_SIGNBIT* cases with CASE_FLT_FN.
gcc/ChangeLog:
* gimple-range-op.cc
(gimple_range_op_handler::maybe_builtin_call): Replace
CFN_BUILTIN_SIGNBIT* cases with CASE_FLT_FN.
---
gcc/gimple-range-op.cc | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/gcc/gimple-range-op.cc b/gcc/gimple-range-op.cc
index 9bdef3d45c0..527893f66af 100644
--- a/gcc/gimple-range-op.cc
+++ b/gcc/gimple-range-op.cc
@@ -756,9 +756,7 @@ gimple_range_op_handler::maybe_builtin_call ()
m_valid = false;
break;
- case CFN_BUILT_IN_SIGNBIT:
- case CFN_BUILT_IN_SIGNBITF:
- case CFN_BUILT_IN_SIGNBITL:
+ CASE_FLT_FN (CFN_BUILT_IN_SIGNBIT):
m_op1 = gimple_call_arg (call, 0);
m_float = &op_cfn_signbit;
m_valid = true;
--
2.37.3
prev parent reply other threads:[~2022-10-14 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 10:03 Aldy Hernandez
2022-10-14 10:16 ` Jakub Jelinek
2022-10-14 14:23 ` Aldy Hernandez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGm3qMXQC9p6LEHYeKWDWgCA_G17dba8vfMDQE_0jhYvmb3Mew@mail.gmail.com \
--to=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).