public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: GCC patches <gcc-patches@gcc.gnu.org>
Cc: Andrew MacLeod <amacleod@redhat.com>, Aldy Hernandez <aldyh@redhat.com>
Subject: [COMMITTED] Add cases for CFN_BUILT_IN_SIGNBIT[FL].
Date: Fri, 14 Oct 2022 12:03:16 +0200	[thread overview]
Message-ID: <20221014100316.568795-1-aldyh@redhat.com> (raw)

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:
       m_op1 = gimple_call_arg (call, 0);
       m_float = &op_cfn_signbit;
       m_valid = true;
-- 
2.37.3


             reply	other threads:[~2022-10-14 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 10:03 Aldy Hernandez [this message]
2022-10-14 10:16 ` Jakub Jelinek
2022-10-14 14:23   ` Aldy Hernandez

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=20221014100316.568795-1-aldyh@redhat.com \
    --to=aldyh@redhat.com \
    --cc=amacleod@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).