public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101856] match_arith_overflow checks only mulv4_optab/umulv4_optab  tables when smul_highpart_optab/umul_highpart_optab can produce decent code too
Date: Fri, 19 May 2023 10:59:02 +0000	[thread overview]
Message-ID: <bug-101856-4-rmyQXKDaKv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101856-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101856

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:62d08a67c83b4a089866c6d19e82d70ee5b8aed1

commit r14-992-g62d08a67c83b4a089866c6d19e82d70ee5b8aed1
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri May 19 12:57:31 2023 +0200

    tree-ssa-math-opts: Pattern recognize hand written __builtin_mul_overflow_p
with same unsigned types even when target just has highpart umul [PR101856]

    As can be seen on the following testcase, we pattern recognize it on
    i?86/x86_64 as return __builtin_mul_overflow_p (x, y, 0UL) and avoid
    that way the extra division, but don't do it e.g. on aarch64 or ppc64le,
    even when return __builtin_mul_overflow_p (x, y, 0UL); actually produces
    there better code.  The reason for testing the presence of the optab
    handler is to make sure the generated code for it is short to ensure
    we don't actually pessimize code instead of optimizing it.
    But, we have one case that the internal-fn.cc .MUL_OVERFLOW expansion
    handles nicely, and that is when arguments/result is the same mode
    TYPE_UNSIGNED type, we only use IMAGPART_EXPR of it (i.e.
    __builtin_mul_overflow_p rather than __builtin_mul_overflow) and
    umul_highpart_optab supports the particular mode, in that case
    we emit comparison of the highpart umul result against zero.

    So, the following patch matches what we do in internal-fn.cc and
    also pattern matches __builtin_mul_overflow_p if
    1) we only need the flag whether it overflowed (i.e. !use_seen)
    2) it is unsigned (i.e. !cast_stmt)
    3) umul_highpart is supported for the mode

    2023-05-19  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/101856
            * tree-ssa-math-opts.cc (match_arith_overflow): Pattern detect
            unsigned __builtin_mul_overflow_p even when umulv4_optab doesn't
            support it but umul_highpart_optab does.

            * gcc.dg/tree-ssa/pr101856.c: New test.

  parent reply	other threads:[~2023-05-19 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  7:22 [Bug tree-optimization/101856] New: " pinskia at gcc dot gnu.org
2022-12-25  5:19 ` [Bug tree-optimization/101856] " pinskia at gcc dot gnu.org
2023-05-18 10:10 ` jakub at gcc dot gnu.org
2023-05-19 10:59 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-19 11:00 ` jakub at gcc dot gnu.org

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=bug-101856-4-rmyQXKDaKv@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).