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 d/96924] d: ICE in create_tmp_var, at gimple-expr.c:482
Date: Fri, 04 Sep 2020 21:02:35 +0000	[thread overview]
Message-ID: <bug-96924-4-yyWasz6oWF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96924-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Iain Buclaw
<ibuclaw@gcc.gnu.org>:

https://gcc.gnu.org/g:40af8b2eff82f28d83b2a5fe153cbc53af665956

commit r10-8711-g40af8b2eff82f28d83b2a5fe153cbc53af665956
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Fri Sep 4 22:54:22 2020 +0200

    d: Fix ICE in create_tmp_var, at gimple-expr.c:482

    Array concatenate expressions were creating more SAVE_EXPRs than what
    was necessary.  The internal error itself was the result of a forced
    temporary being made on a TREE_ADDRESSABLE type.

    gcc/d/ChangeLog:

            PR d/96924
            * expr.cc (ExprVisitor::visit (CatAssignExp *)): Don't force
            temporaries needlessly.

    gcc/testsuite/ChangeLog:

            PR d/96924
            * gdc.dg/pr96924.d: New test.

    (cherry picked from commit 52908b8de15a1c762a73063f1162bcedfcc993b4)

  parent reply	other threads:[~2020-09-04 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 14:08 [Bug d/96924] New: " ibuclaw at gdcproject dot org
2020-09-04 21:02 ` [Bug d/96924] " cvs-commit at gcc dot gnu.org
2020-09-04 21:02 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-04 21:06 ` ibuclaw at gdcproject dot 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-96924-4-yyWasz6oWF@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).