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/101741] [12 Regression] ICE in fold_stmt, at gimple-range-fold.cc:541 since r12-2517-g1ce0b26e6e1e6c34
Date: Mon, 09 Aug 2021 20:25:04 +0000	[thread overview]
Message-ID: <bug-101741-4-2rP20PtKSH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101741-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:c86c95edd165d674614516cda0b1fcb6616c1096

commit r12-2826-gc86c95edd165d674614516cda0b1fcb6616c1096
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Mon Aug 9 15:53:42 2021 -0400

    Ensure toupper and tolower follow the expected pattern.

    If the parameter is not compatible with the LHS, assume this is not really
a
    builtin function to avoid a trap.

            gcc/
            PR tree-optimization/101741
            * gimple-range-fold.cc (fold_using_range::range_of_builtin_call):
Check
            type of parameter for toupper/tolower.

            gcc/testsuite/
            * gcc.dg/pr101741.c: New.

  parent reply	other threads:[~2021-08-09 20:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03  6:41 [Bug tree-optimization/101741] New: [12 Regression] ICE in fold_stmt, at gimple-range-fold.cc:541 asolokha at gmx dot com
2021-08-03 11:33 ` [Bug tree-optimization/101741] [12 Regression] ICE in fold_stmt, at gimple-range-fold.cc:541 since r12-2517-g1ce0b26e6e1e6c34 marxin at gcc dot gnu.org
2021-08-03 11:46 ` asolokha at gmx dot com
2021-08-03 11:55 ` marxin at gcc dot gnu.org
2021-08-03 20:05 ` msebor at gcc dot gnu.org
2021-08-09 20:25 ` cvs-commit at gcc dot gnu.org [this message]
2021-08-09 20:26 ` amacleod at redhat dot com
2022-11-28 22:51 ` 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-101741-4-2rP20PtKSH@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).