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 middle-end/104721] currently_expanding_gimple_stmt isn't cleared properly
Date: Tue, 01 Mar 2022 14:18:43 +0000	[thread overview]
Message-ID: <bug-104721-4-gXyEJGia6s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104721-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:88f91d8ccc8fec3a811975e3e4765b9a94d3f764

commit r12-7429-g88f91d8ccc8fec3a811975e3e4765b9a94d3f764
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Mon Feb 28 15:18:04 2022 -0800

    Clear currently_expanding_gimple_stmt properly

    commit a5883ba0de68efad36db145e75c86394d8bd44ea
    Author: Michael Matz <matz@gcc.gnu.org>
    Date:   Tue Nov 24 15:37:32 2009 +0000

    introduced currently_expanding_gimple_stmt, which was set and cleared in
    expand_gimple_basic_block when expanding gimple statement to RTL.  But it
    isn't cleared when expand_gimple_basic_block returns inside the loop.

            PR middle-end/104721
            * cfgexpand.cc (expand_gimple_basic_block): Clear
            currently_expanding_gimple_stmt when returning inside the loop.

  parent reply	other threads:[~2022-03-01 14:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 23:17 [Bug middle-end/104721] New: " hjl.tools at gmail dot com
2022-02-28 23:43 ` [Bug middle-end/104721] " hjl.tools at gmail dot com
2022-02-28 23:43 ` hjl.tools at gmail dot com
2022-03-01 12:53 ` matz at gcc dot gnu.org
2022-03-01 13:56 ` hjl.tools at gmail dot com
2022-03-01 14:04 ` jakub at gcc dot gnu.org
2022-03-01 14:18 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-03  3:19 ` hjl.tools at gmail dot com

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-104721-4-gXyEJGia6s@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).