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/108877] Explicit immutable struct import internal compiler error
Date: Fri, 03 Mar 2023 02:33:23 +0000	[thread overview]
Message-ID: <bug-108877-4-0wHZSEuRLY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108877-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 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:fe6cd1ba23ecbce9c0206c08db182cb5164e3b7d

commit r11-10554-gfe6cd1ba23ecbce9c0206c08db182cb5164e3b7d
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Mon Feb 27 20:46:18 2023 +0100

    d: Fix ICE on explicit immutable struct import [PR108877]

    Const and immutable types are built as variants of the type they are
    derived from, and TYPE_STUB_DECL is not set for these variants.

            PR d/108877

    gcc/d/ChangeLog:

            * imports.cc (ImportVisitor::visit (EnumDeclaration *)): Call
            make_import on TYPE_MAIN_VARIANT.
            (ImportVisitor::visit (AggregateDeclaration *)): Likewise.
            (ImportVisitor::visit (ClassDeclaration *)): Likewise.

    gcc/testsuite/ChangeLog:

            * gdc.dg/imports/pr108877a.d: New test.
            * gdc.dg/pr108877.d: New test.

    (cherry picked from commit ce1cea3e22f58bbddde017f8a92e59bae8892339)

  parent reply	other threads:[~2023-03-03  2:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 20:04 [Bug d/108877] New: " belka at caraus dot de
2023-02-26  0:17 ` [Bug d/108877] " ibuclaw at gcc dot gnu.org
2023-02-27 12:39 ` belka at caraus dot de
2023-03-03  0:26 ` cvs-commit at gcc dot gnu.org
2023-03-03  2:28 ` cvs-commit at gcc dot gnu.org
2023-03-03  2:33 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-03  2:43 ` cvs-commit at gcc dot gnu.org
2023-03-03  2:46 ` ibuclaw 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-108877-4-0wHZSEuRLY@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).