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/100964] d: TypeInfo error when using slice copy on Structs with -fno-rtti
Date: Wed, 09 Jun 2021 18:01:52 +0000	[thread overview]
Message-ID: <bug-100964-4-15yLXfzapn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100964-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:10d4f283f4177d80cec3c9e8bf447a48cab5bb47

commit r11-8536-g10d4f283f4177d80cec3c9e8bf447a48cab5bb47
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Wed Jun 9 19:39:28 2021 +0200

    d: TypeInfo error when using slice copy on Structs (PR100964)

    Known limitation: does not work for struct with postblit or dtor.

    gcc/d/ChangeLog:

            PR d/100964
            * dmd/expression.c (Expression::checkPostblit): Don't generate
            TypeInfo when RTTI is disabled.

    gcc/testsuite/ChangeLog:

            PR d/100964
            * gdc.test/compilable/betterCarray.d: Add test cases.

    (cherry picked from commit 036e14ca44eaddf329a79d56d556862118b1f220)

  parent reply	other threads:[~2021-06-09 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 11:26 [Bug d/100964] New: " ibuclaw at gdcproject dot org
2021-06-09 18:00 ` [Bug d/100964] " cvs-commit at gcc dot gnu.org
2021-06-09 18:01 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-09 18:03 ` cvs-commit at gcc dot gnu.org
2021-06-09 18:04 ` cvs-commit at gcc dot gnu.org
2021-06-09 18: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-100964-4-15yLXfzapn@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).