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++/99239] [modules] internal compiler error: in duplicate_decls
Date: Tue, 23 Mar 2021 12:21:30 +0000	[thread overview]
Message-ID: <bug-99239-4-ihRqCzifUS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99239-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:6acd6692f1ac3c2ece3da36178df73e3b12c4f65

commit r11-7785-g6acd6692f1ac3c2ece3da36178df73e3b12c4f65
Author: Nathan Sidwell <nathan@acm.org>
Date:   Tue Mar 23 05:18:04 2021 -0700

    c++: Over-zealous assert [PR 99239]

    This was simply an overzealous assert.  Possibly correct thinking at
    the time that code was written, but not true now.  Of course we can
    have imported artificial decls.

            PR c++/99239
            gcc/cp/
            * decl.c (duplicate_decls): Remove assert about maybe-imported
            artificial decls.
            gcc/testsuite/
            * g++.dg/modules/pr99239_a.H: New.
            * g++.dg/modules/pr99239_b.H: New.

  parent reply	other threads:[~2021-03-23 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  8:37 [Bug c++/99239] New: " alexander.lelyakin at googlemail dot com
2021-03-09  7:53 ` [Bug c++/99239] " alexander.lelyakin at googlemail dot com
2021-03-09  8:16 ` alexander.lelyakin at googlemail dot com
2021-03-23 12:21 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-23 12:22 ` nathan 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-99239-4-ihRqCzifUS@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).