public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/96194] [10/11 Regression] ICE in assign_temp, at function.c:984 during RTL pass: expand
Date: Tue, 14 Jul 2020 11:09:24 +0000 [thread overview]
Message-ID: <bug-96194-4-ZjDG6O7jDS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96194-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96194
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
--- gcc/expr.c.jj 2020-07-13 19:09:33.173872178 +0200
+++ gcc/expr.c 2020-07-14 13:07:26.228801996 +0200
@@ -8382,7 +8382,9 @@ expand_constructor (tree exp, rtx target
|| GET_CODE (target) == PARALLEL || modifier == EXPAND_STACK_PARM
/* Also make a temporary if the store is to volatile memory, to
avoid individual accesses to aggregate members. */
- || (GET_CODE (target) == MEM && MEM_VOLATILE_P (target)))
+ || (GET_CODE (target) == MEM
+ && MEM_VOLATILE_P (target)
+ && !TREE_ADDRESSABLE (TREE_TYPE (exp))))
{
if (avoid_temp_mem)
return NULL_RTX;
fixes this - even when volatile, for non-POD types the middle-end may not
create temporaries period.
next prev parent reply other threads:[~2020-07-14 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 8:12 [Bug c++/96194] New: 10.1.1: " manuel.lauss at googlemail dot com
2020-07-14 10:53 ` [Bug middle-end/96194] " jakub at gcc dot gnu.org
2020-07-14 11:02 ` [Bug middle-end/96194] [10/11 Regression] " jakub at gcc dot gnu.org
2020-07-14 11:09 ` jakub at gcc dot gnu.org [this message]
2020-07-14 11:10 ` jakub at gcc dot gnu.org
2020-07-14 11:22 ` jakub at gcc dot gnu.org
2020-07-14 12:03 ` manuel.lauss at googlemail dot com
2020-07-14 14:03 ` cvs-commit at gcc dot gnu.org
2020-07-14 14:04 ` cvs-commit at gcc dot gnu.org
2020-07-14 14:08 ` jakub at gcc dot gnu.org
2020-07-23 1:29 ` hp 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-96194-4-ZjDG6O7jDS@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).