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-3903] [range-ops] Remove specialized fold_range methods for various operators. Date: Fri, 11 Nov 2022 13:54:00 +0000 (GMT) [thread overview] Message-ID: <20221111135400.0B1EC385840C@sourceware.org> (raw) https://gcc.gnu.org/g:e0cfde7e8b36a8176b661af16dff91ebf4f99a8e commit r13-3903-ge0cfde7e8b36a8176b661af16dff91ebf4f99a8e Author: Aldy Hernandez <aldyh@redhat.com> Date: Thu Nov 10 11:27:52 2022 +0100 [range-ops] Remove specialized fold_range methods for various operators. Remove some specialized fold_range methods that were merely setting maybe nonzero masks, as these are now subsumed by the generic version. gcc/ChangeLog: * range-op.cc (operator_mult::fold_range): Remove. (operator_div::fold_range): Remove. (operator_bitwise_and): Remove. Diff: --- gcc/range-op.cc | 52 ---------------------------------------------------- 1 file changed, 52 deletions(-) diff --git a/gcc/range-op.cc b/gcc/range-op.cc index 0b01cf48fdf..6fa3b151596 100644 --- a/gcc/range-op.cc +++ b/gcc/range-op.cc @@ -1790,13 +1790,9 @@ cross_product_operator::wi_cross_product (irange &r, tree type, class operator_mult : public cross_product_operator { - using range_operator::fold_range; using range_operator::op1_range; using range_operator::op2_range; public: - virtual bool fold_range (irange &r, tree type, - const irange &lh, const irange &rh, - relation_trio = TRIO_VARYING) const final override; virtual void wi_fold (irange &r, tree type, const wide_int &lh_lb, const wide_int &lh_ub, @@ -1815,18 +1811,6 @@ public: relation_trio) const final override; } op_mult; -bool -operator_mult::fold_range (irange &r, tree type, - const irange &lh, const irange &rh, - relation_trio trio) const -{ - if (!cross_product_operator::fold_range (r, type, lh, rh, trio)) - return false; - - update_known_bitmask (r, MULT_EXPR, lh, rh); - return true; -} - bool operator_mult::op1_range (irange &r, tree type, const irange &lhs, const irange &op2, @@ -1979,23 +1963,8 @@ public: virtual bool wi_op_overflows (wide_int &res, tree type, const wide_int &, const wide_int &) const final override; - virtual bool fold_range (irange &r, tree type, - const irange &lh, const irange &rh, - relation_trio trio) const final override; }; -bool -operator_div::fold_range (irange &r, tree type, - const irange &lh, const irange &rh, - relation_trio trio) const -{ - if (!cross_product_operator::fold_range (r, type, lh, rh, trio)) - return false; - - update_known_bitmask (r, m_code, lh, rh); - return true; -} - bool operator_div::wi_op_overflows (wide_int &res, tree type, const wide_int &w0, const wide_int &w1) const @@ -2834,14 +2803,9 @@ operator_logical_and::op2_range (irange &r, tree type, class operator_bitwise_and : public range_operator { - using range_operator::fold_range; using range_operator::op1_range; using range_operator::op2_range; public: - virtual bool fold_range (irange &r, tree type, - const irange &lh, - const irange &rh, - relation_trio rel = TRIO_VARYING) const; virtual bool op1_range (irange &r, tree type, const irange &lhs, const irange &op2, @@ -2865,22 +2829,6 @@ private: const irange &op2) const; } op_bitwise_and; -bool -operator_bitwise_and::fold_range (irange &r, tree type, - const irange &lh, - const irange &rh, - relation_trio) const -{ - if (range_operator::fold_range (r, type, lh, rh)) - { - if (!r.undefined_p () && !lh.undefined_p () && !rh.undefined_p ()) - r.set_nonzero_bits (wi::bit_and (lh.get_nonzero_bits (), - rh.get_nonzero_bits ())); - return true; - } - return false; -} - // Optimize BIT_AND_EXPR, BIT_IOR_EXPR and BIT_XOR_EXPR of signed types // by considering the number of leading redundant sign bit copies.
reply other threads:[~2022-11-11 13:54 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=20221111135400.0B1EC385840C@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).