public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alexander.lelyakin at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99239] [modules] internal compiler error: in duplicate_decls
Date: Tue, 09 Mar 2021 08:16:34 +0000 [thread overview]
Message-ID: <bug-99239-4-5Fzog8AViS@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 #2 from Alexander Lelyakin <alexander.lelyakin at googlemail dot com> ---
(In reply to Alexander Lelyakin from comment #1)
> About half of sequences of headers producing segmentation fault are stopped
> on <stop_token>.
> However there are another variants:
> ----
> g++ -std=c++20 -fmodules-ts -x c++-system-header stdexcept
> g++ -std=c++20 -fmodules-ts -x c++-system-header locale
Sorry this was for another bug
next prev parent reply other threads:[~2021-03-09 8:16 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 [this message]
2021-03-23 12:21 ` cvs-commit at gcc dot gnu.org
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-5Fzog8AViS@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).