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 sanitizer/112741] ICE: in gimplify_var_or_parm_decl, at gimplify.cc:3261
Date: Tue, 28 Nov 2023 15:58:52 +0000	[thread overview]
Message-ID: <bug-112741-4-L7fGBw4RBw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112741-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from GCC 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:f45d5e30bd98ea1d8dc29841a06b2cfa5662deb5

commit r14-5935-gf45d5e30bd98ea1d8dc29841a06b2cfa5662deb5
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Nov 28 12:49:35 2023 +0100

    middle-end/112741 - ICE with gimple FE and later regimplification

    The GIMPLE frontend, when bypassing gimplification, doesn't set
    DECL_SEEN_IN_BIND_EXPR_P given there are no such things in GIMPLE.
    But it probably should set the flag anyway to avoid later ICEs
    when regimplifying.

            PR middle-end/112741
    gcc/c/
            * gimple-parser.cc (c_parser_parse_gimple_body): Also
            set DECL_SEEN_IN_BIND_EXPR_Pfor locals.

    gcc/testsuite/
            * gcc.dg/ubsan/pr112741.c: New testcase.

  parent reply	other threads:[~2023-11-28 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  7:39 [Bug sanitizer/112741] New: " iamanonymous.cs at gmail dot com
2023-11-28  7:46 ` [Bug sanitizer/112741] " sjames at gcc dot gnu.org
2023-11-28 11:46 ` rguenth at gcc dot gnu.org
2023-11-28 15:58 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-28 15:59 ` 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-112741-4-L7fGBw4RBw@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).