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/101490] ICE at convert_expr(tree_node*, Type*, Type*)
Date: Wed, 28 Jul 2021 11:36:55 +0000	[thread overview]
Message-ID: <bug-101490-4-Ofj04VYfPX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101490-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 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:45be6e80884d452c927c24e43b9018e2aa141c64

commit r11-8809-g45be6e80884d452c927c24e43b9018e2aa141c64
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Mon Jul 26 15:11:42 2021 +0200

    d: fix ICE at convert_expr(tree_node*, Type*, Type*) (PR101490)

    Both the front-end and code generator had a modulo by zero bug when testing
if
    a conversion from a static array to dynamic array was valid.

            PR d/101490

    gcc/d/ChangeLog:

            * d-codegen.cc (build_array_index): Handle void arrays same as
byte.
            * d-convert.cc (convert_expr): Handle converting to zero-sized
arrays.
            * dmd/dcast.c (castTo): Handle casting to zero-sized arrays.

    gcc/testsuite/ChangeLog:

            * gdc.dg/pr101490.d: New test.
            * gdc.test/fail_compilation/fail22144.d: New test.

    (cherry picked from commit c936c39f86c74b3bfc6831f694b3165296c99dc0)

  parent reply	other threads:[~2021-07-28 11:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17 18:00 [Bug d/101490] New: " SztfG at yandex dot ru
2021-07-25 23:10 ` [Bug d/101490] " ibuclaw at gdcproject dot org
2021-07-28 11:18 ` cvs-commit at gcc dot gnu.org
2021-07-28 11:36 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-28 11:50 ` cvs-commit at gcc dot gnu.org
2021-07-28 11:57 ` cvs-commit at gcc dot gnu.org
2021-07-28 12:47 ` 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-101490-4-Ofj04VYfPX@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).