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 c/105597] ice in type, at value-range.h:223
Date: Fri, 13 May 2022 18:41:30 +0000	[thread overview]
Message-ID: <bug-105597-4-kwuLcYU92A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105597-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 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:e97e99296505e6015bc9e281364818bb89ca8a49

commit r13-449-ge97e99296505e6015bc9e281364818bb89ca8a49
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Fri May 13 13:11:18 2022 -0400

    Check operand for type, not LHS.

    When folding, the LHS has not been set, so we should be checking the type
of
    op1.  We should also make sure op1 is not undefined.

            PR tree-optimization/105597
            gcc/
            * range-op.cc (operator_minus::lhs_op1_relation): Use op1 instead
            of the lhs and make sure it is not undefined.
            gcc/testsuite/
            * gcc.dg/pr105597.c: New.

  parent reply	other threads:[~2022-05-13 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 17:03 [Bug c/105597] New: " dcb314 at hotmail dot com
2022-05-13 17:07 ` [Bug c/105597] " dcb314 at hotmail dot com
2022-05-13 17:14 ` amacleod at redhat dot com
2022-05-13 17:21 ` dcb314 at hotmail dot com
2022-05-13 17:21 ` mpolacek at gcc dot gnu.org
2022-05-13 18:41 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-13 18:42 ` amacleod at redhat dot com
2022-10-28 20:19 ` [Bug tree-optimization/105597] [13 Regression] " 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-105597-4-kwuLcYU92A@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).