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/91029] missed optimization regarding value of modulo operation
Date: Tue, 17 Nov 2020 22:01:02 +0000	[thread overview]
Message-ID: <bug-91029-4-WHlEfcICVw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91029-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:1e27e7a582a9b86bcf86f5c103cd947672746e97

commit r11-5111-g1e27e7a582a9b86bcf86f5c103cd947672746e97
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Tue Nov 17 14:47:58 2020 -0500

    recognize implied ranges for modulo.

    implement op1_range for modulo with implied positive and negative ranges.

            gcc/
            PR tree-optimization/91029
            * range-op.cc (operator_trunc_mod::op1_range): New.
            gcc/testsuite/
            * gcc.dg/pr91029.c: New.

       reply	other threads:[~2020-11-17 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91029-4@http.gcc.gnu.org/bugzilla/>
2020-11-17 22:01 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-17 23:07 ` amacleod at redhat dot com
2020-11-18  0:50 ` bruno at clisp dot org
2020-11-18 21:17 ` cvs-commit at gcc dot gnu.org
2020-11-18 22:23 ` jakub at gcc dot gnu.org
2020-11-19  1:16 ` bruno at clisp dot org
2020-11-19 12:22 ` jakub at gcc dot gnu.org
2020-11-19 15:32 ` amacleod at redhat dot com
2020-11-19 19:55 ` jakub at gcc dot gnu.org
2020-11-19 23:03 ` cvs-commit at gcc dot gnu.org
2023-11-26 13:16 ` pinskia 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-91029-4-WHlEfcICVw@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).