public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Optimize divmod expansion (PR middle-end/79665)
Date: Thu, 23 Feb 2017 06:00:00 -0000	[thread overview]
Message-ID: <e6308265-e2d4-fbf6-e9fd-69ee5fec9abe@redhat.com> (raw)
In-Reply-To: <20170222214046.GA1849@tucnak>

On 02/22/2017 02:40 PM, Jakub Jelinek wrote:
> Hi!
>
> If both arguments of integer division or modulo are known to be non-negative
> in corresponding signed type, then signed as well as unsigned division/modulo
> shall have the exact same result and therefore we can choose between those
> two depending on which one is faster (or shorter for -Os), which varries
> a lot depending on target and especially for constant divisors on the exact
> divisor.  expand_divmod itself is too complicated and we don't even have
> the ability to ask about costs e.g. for highpart multiplication without
> actually expanding it, so this patch just in that case tries both sequences,
> computes their costs and uses the cheaper (and for equal cost honors the
> actual original signedness of the operation).
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> 2017-02-22  Jakub Jelinek  <jakub@redhat.com>
>
> 	PR middle-end/79665
> 	* internal-fn.c (get_range_pos_neg): Moved to ...
> 	* tree.c (get_range_pos_neg): ... here.  No longer static.
> 	* tree.h (get_range_pos_neg): New prototype.
> 	* expr.c (expand_expr_real_2) <case TRUNC_DIV_EXPR>: If both arguments
> 	are known to be in between 0 and signed maximum inclusive, try to
> 	expand both unsigned and signed divmod and use the cheaper one from
> 	those.
OK.
jeff

  reply	other threads:[~2017-02-23  5:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 21:50 Jakub Jelinek
2017-02-23  6:00 ` Jeff Law [this message]
2017-05-31  8:15   ` Georg-Johann Lay
2017-05-31  8:19     ` Jakub Jelinek
2017-05-31  9:00       ` Georg-Johann Lay
2017-05-31  9:08         ` Jakub Jelinek
2017-05-31 14:04           ` Georg-Johann Lay

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=e6308265-e2d4-fbf6-e9fd-69ee5fec9abe@redhat.com \
    --to=law@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).