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/94826] [8/9 regression] ICE in gcc.dg/pr94780.c after r10-7999 Date: Wed, 16 Sep 2020 19:21:25 +0000 [thread overview] Message-ID: <bug-94826-4-eohQKV3AGx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94826-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94826 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:540e1de23a70360fe9b626df8420be704d02e3a7 commit r9-8890-g540e1de23a70360fe9b626df8420be704d02e3a7 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Apr 29 15:55:39 2020 +0200 rs6000: Fix rs6000_atomic_assign_expand_fenv [PR94826] This is the rs6000 version of the earlier committed x86, aarch64 and arm fixes, as create_tmp_var_raw is used because the C FE can call this outside of function context, we need to make sure the first references to those VAR_DECLs are through a TARGET_EXPR, so that it gets gimple_add_tmp_var marked in whatever function it gets expanded in. Without that DECL_CONTEXT is NULL and the vars aren't added as local decls of the containing function. 2020-04-29 Jakub Jelinek <jakub@redhat.com> PR target/94826 * config/rs6000/rs6000.c (rs6000_atomic_assign_expand_fenv): Use TARGET_EXPR instead of MODIFY_EXPR for first assignment to fenv_var, fenv_clear and old_fenv variables. For fenv_addr take address of TARGET_EXPR of fenv_var with void_node initializer. Formatting fixes. (cherry picked from commit c7137fcc7cbc1f1f14f9fed75adcc6bd8f1d418c)
next prev parent reply other threads:[~2020-09-16 19:21 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-28 17:24 [Bug other/94826] New: [10 " seurer at linux dot vnet.ibm.com 2020-04-28 21:53 ` [Bug target/94826] " pinskia at gcc dot gnu.org 2020-04-29 6:56 ` [Bug target/94826] [8/9/10 " rguenth at gcc dot gnu.org 2020-04-29 7:38 ` jakub at gcc dot gnu.org 2020-04-29 13:56 ` cvs-commit at gcc dot gnu.org 2020-04-29 13:56 ` [Bug target/94826] [8/9 " jakub at gcc dot gnu.org 2020-07-31 0:01 ` bergner at gcc dot gnu.org 2020-09-16 19:21 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-17 17:40 ` jakub 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-94826-4-eohQKV3AGx@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: linkBe 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).