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 target/94780] [8/9 Regression] ICE in walk_body at gcc/tree-nested.c:713 since r6-3632-gf6f69fb09c5f81df
Date: Sat, 31 Jul 2021 05:21:02 +0000 [thread overview]
Message-ID: <bug-94780-4-9MVJcVj90e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94780-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94780
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Xi Ruoyao <xry111@gcc.gnu.org>:
https://gcc.gnu.org/g:613e4ebc9c6a156f9efc656a2f2620ab22fc6b52
commit r10-10016-g613e4ebc9c6a156f9efc656a2f2620ab22fc6b52
Author: Xi Ruoyao <xry111@mengyan1223.wang>
Date: Fri Jul 30 23:44:14 2021 +0800
mips: Fix up mips_atomic_assign_expand_fenv [PR94780]
Commit message shamelessly copied from 1777beb6b129 by jakub:
This function, because it is sometimes called even outside of function
bodies, uses create_tmp_var_raw rather than create_tmp_var. But in order
for that to work, when first referenced, the VAR_DECLs need to appear in a
TARGET_EXPR so that during gimplification the var gets the right
DECL_CONTEXT and is added to local decls.
gcc/
PR target/94780
* config/mips/mips.c (mips_atomic_assign_expand_fenv): Use
TARGET_EXPR instead of MODIFY_EXPR.
(cherry picked from commit 2065654435e3d97676366f82b939bc9273382dbe)
next prev parent reply other threads:[~2021-07-31 5:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 1:15 [Bug c/94780] New: [9/10] internal compiler error: Segmentation fault anbu1024.me at gmail dot com
2020-04-27 4:27 ` [Bug c/94780] [8/9/10 Regression] ICE in walk_body at gcc/tree-nested.c:713 since r6-3632-gf6f69fb09c5f81df marxin at gcc dot gnu.org
2020-04-27 4:27 ` marxin at gcc dot gnu.org
2020-04-27 7:03 ` rguenth at gcc dot gnu.org
2020-04-27 9:23 ` asolokha at gmx dot com
2020-04-27 12:37 ` jakub at gcc dot gnu.org
2020-04-27 13:28 ` [Bug target/94780] " jakub at gcc dot gnu.org
2020-04-27 21:29 ` cvs-commit at gcc dot gnu.org
2020-04-27 21:58 ` [Bug target/94780] [8/9 " jakub at gcc dot gnu.org
2020-05-03 16:45 ` schwab@linux-m68k.org
2020-05-07 16:14 ` wilson at gcc dot gnu.org
2020-05-08 2:55 ` paul.hua.gm at gmail dot com
2020-09-16 19:21 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:38 ` jakub at gcc dot gnu.org
2021-06-23 3:15 ` xry111 at mengyan1223 dot wang
2021-07-30 16:58 ` cvs-commit at gcc dot gnu.org
2021-07-31 5:21 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-31 10:24 ` cvs-commit 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-94780-4-9MVJcVj90e@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).