public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-3307] Implement range-op entry for __builtin_copysign. Date: Fri, 14 Oct 2022 16:43:15 +0000 (GMT) [thread overview] Message-ID: <20221014164315.BEEE33858C62@sourceware.org> (raw) https://gcc.gnu.org/g:8efc38347a7444dde3fb173f0f2c59a60b7db53d commit r13-3307-g8efc38347a7444dde3fb173f0f2c59a60b7db53d Author: Aldy Hernandez <aldyh@redhat.com> Date: Thu Oct 13 17:51:29 2022 +0200 Implement range-op entry for __builtin_copysign. copysign(MAGNITUDE, SIGN) is implemented as the absolute of MAGNITUDE, with SIGN applied. If the sign of "SIGN" cannot be determined, we return a range of [-MAGNITUDE, +MAGNITUDE]. gcc/ChangeLog: * gimple-range-op.cc (class cfn_copysign): New. (gimple_range_op_handler::maybe_builtin_call): Add CFN_BUILT_IN_COPYSIGN*. Diff: --- gcc/gimple-range-op.cc | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/gcc/gimple-range-op.cc b/gcc/gimple-range-op.cc index 527893f66af..2662319aadc 100644 --- a/gcc/gimple-range-op.cc +++ b/gcc/gimple-range-op.cc @@ -342,6 +342,38 @@ public: } } op_cfn_signbit; +// Implement range operator for CFN_BUILT_IN_COPYSIGN +class cfn_copysign : public range_operator_float +{ +public: + using range_operator_float::fold_range; + virtual bool fold_range (frange &r, tree type, const frange &lh, + const frange &rh, relation_kind) const override + { + frange neg; + range_op_handler abs_op (ABS_EXPR, type); + range_op_handler neg_op (NEGATE_EXPR, type); + if (!abs_op || !abs_op.fold_range (r, type, lh, frange (type))) + return false; + if (!neg_op || !neg_op.fold_range (neg, type, r, frange (type))) + return false; + + bool signbit; + if (rh.signbit_p (signbit)) + { + // If the sign is negative, flip the result from ABS, + // otherwise leave things positive. + if (signbit) + r = neg; + } + else + // If the sign is unknown, keep the positive and negative + // alternatives. + r.union_ (neg); + return true; + } +} op_cfn_copysign; + // Implement range operator for CFN_BUILT_IN_TOUPPER and CFN_BUILT_IN_TOLOWER. class cfn_toupper_tolower : public range_operator { @@ -762,6 +794,13 @@ gimple_range_op_handler::maybe_builtin_call () m_valid = true; break; + CASE_CFN_COPYSIGN_ALL: + m_op1 = gimple_call_arg (call, 0); + m_op2 = gimple_call_arg (call, 1); + m_float = &op_cfn_copysign; + m_valid = true; + break; + case CFN_BUILT_IN_TOUPPER: case CFN_BUILT_IN_TOLOWER: // Only proceed If the argument is compatible with the LHS.
reply other threads:[~2022-10-14 16:43 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221014164315.BEEE33858C62@sourceware.org \ --to=aldyh@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).