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/107898] [11/12/13 Regression] ICE in irange_intersect, at value-range.cc:1640
Date: Tue, 29 Nov 2022 09:26:05 +0000	[thread overview]
Message-ID: <bug-107898-4-aBYuugmq84@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107898-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:9948daa4fd0f0ea0a9d56c2fefe1bca478554d27

commit r13-4385-g9948daa4fd0f0ea0a9d56c2fefe1bca478554d27
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Nov 29 09:03:46 2022 +0100

    tree-optimization/107898 - ICE with -Walloca-larger-than

    The following avoids ICEing with a mismatched prototype for alloca
    and -Walloca-larger-than using irange for checks which doesn't
    like mismatched types.

            PR tree-optimization/107898
            * gimple-ssa-warn-alloca.cc (alloca_call_type): Check
            the type of the alloca argument is compatible with size_t
            before querying ranges.

  parent reply	other threads:[~2022-11-29  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 17:58 [Bug c/107898] New: " gscfq@t-online.de
2022-11-28 18:15 ` [Bug tree-optimization/107898] " pinskia at gcc dot gnu.org
2022-11-29  8:03 ` [Bug c/107898] " rguenth at gcc dot gnu.org
2022-11-29  9:26 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-29  9:27 ` [Bug c/107898] [11/12 " rguenth at gcc dot gnu.org
2022-11-29 14:29 ` amacleod at redhat dot com
2022-12-12 11:21 ` cvs-commit at gcc dot gnu.org
2023-05-05 13:34 ` [Bug c/107898] [11 " cvs-commit at gcc dot gnu.org
2023-05-05 13:34 ` rguenth 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-107898-4-aBYuugmq84@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).