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 c++/99245] [modules] ICE in write_cluster, at cp/module.cc:14600
Date: Fri, 05 Mar 2021 20:54:04 +0000	[thread overview]
Message-ID: <bug-99245-4-wkbdbdhTB2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99245-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>:

https://gcc.gnu.org/g:9e64dd6b3f6706de571c6ed3c4b7a8c8b67f22b7

commit r11-7532-g9e64dd6b3f6706de571c6ed3c4b7a8c8b67f22b7
Author: Nathan Sidwell <nathan@acm.org>
Date:   Fri Mar 5 12:49:34 2021 -0800

    c++: Duplicate namespace bindings [PR 99245]

    Header units can declare the same entity, and this can lead to one of
    them containing a (non-using) binding to an import.  If one gets the
    cluster ordering just right, an assert will trigger.  Relax that assert.

            PR c++/99245
            gcc/cp/
            * module.cc (module_state::write_cluster): Relax binding assert.
            gcc/testsuite/
            * g++.dg/modules/pr99245_a.H: New.
            * g++.dg/modules/pr99245_b.H: New.

  parent reply	other threads:[~2021-03-05 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  8:47 [Bug c++/99245] New: internal compiler error: " alexander.lelyakin at googlemail dot com
2021-02-28 18:54 ` [Bug c++/99245] [modules] ICE " alexander.lelyakin at googlemail dot com
2021-03-05 19:51 ` nathan at gcc dot gnu.org
2021-03-05 20:54 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-05 20:54 ` nathan at gcc dot gnu.org
2021-12-29 23:04 ` pinskia 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-99245-4-wkbdbdhTB2@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).