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/107029] [13 Regression] ice during GIMPLE pass: reassoc
Date: Tue, 27 Sep 2022 06:27:09 +0000	[thread overview]
Message-ID: <bug-107029-4-SIJAmzuk8Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107029-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:cb8f25c5dc9f6d5207c826c2dafe25f68458ceaf

commit r13-2891-gcb8f25c5dc9f6d5207c826c2dafe25f68458ceaf
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Sep 27 08:26:18 2022 +0200

    reassoc: Handle OFFSET_TYPE like POINTER_TYPE in
optimize_range_tests_cmp_bitwise [PR107029[

    As the testcase shows, OFFSET_TYPE needs the same treatment as
    POINTER_TYPE/REFERENCE_TYPE, otherwise we fail the same during the
    newly added verification.  OFFSET_TYPE is signed though, so unlike
    POINTER_TYPE/REFERENCE_TYPE it can also trigger with the
    x < 0 && y < 0 && z < 0 to (x | y | z) < 0
    optimization.

    2022-09-27  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/107029
            * tree-ssa-reassoc.cc (optimize_range_tests_cmp_bitwise): Treat
            OFFSET_TYPE like POINTER_TYPE, except that OFFSET_TYPE may be
            signed and so can trigger even the (b % 4) == 3 case.

            * g++.dg/torture/pr107029.C: New test.

  parent reply	other threads:[~2022-09-27  6:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 19:34 [Bug c++/107029] New: " dcb314 at hotmail dot com
2022-09-24 20:07 ` [Bug c++/107029] [13 Regression] " jakub at gcc dot gnu.org
2022-09-25 12:52 ` [Bug tree-optimization/107029] " jakub at gcc dot gnu.org
2022-09-27  6:27 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-27 11:08 ` 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-107029-4-SIJAmzuk8Y@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).