public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wendellcraigbaker at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108488] segfault with -fmodules-ts and class-scope friend declaration first in uninstantiated template Date: Sat, 21 Jan 2023 02:35:53 +0000 [thread overview] Message-ID: <bug-108488-4-ohRU2KvNxQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108488-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108488 --- Comment #3 from Wendell Baker <wendellcraigbaker at gmail dot com> --- Created attachment 54324 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54324&action=edit shell script and C++ to demonstrate with <map> and <unordered_map> in combination This happens in real life with the confluence of <map> and <unordered_map> as the accompanying exhibition highlights.
next prev parent reply other threads:[~2023-01-21 2:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-20 22:42 [Bug c++/108488] New: " wendellcraigbaker at gmail dot com 2023-01-20 22:47 ` [Bug c++/108488] " wendellcraigbaker at gmail dot com 2023-01-20 22:48 ` wendellcraigbaker at gmail dot com 2023-01-21 2:35 ` wendellcraigbaker at gmail dot com [this message] 2023-01-24 3:27 ` 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-108488-4-ohRU2KvNxQ@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: linkBe 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).