public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "remi.galanalfonso at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98417] ICE when using C++ modules and -g Date: Tue, 26 Apr 2022 20:29:00 +0000 [thread overview] Message-ID: <bug-98417-4-KvYlvVKkrx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98417-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98417 Rémi Galan Alfonso <remi.galanalfonso at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |remi.galanalfonso at gmail dot com --- Comment #2 from Rémi Galan Alfonso <remi.galanalfonso at gmail dot com> --- Hello, I'm unable to reproduce it on any released gcc-11 or on trunk (but can with a gcc from 2020-12-20). Reduction gives me for hello.cc: module; # 1 "" 1 namespace std { template<class > struct char_traits; } typedef struct {} mbstate_t; namespace std { template<> struct char_traits<char> { mbstate_t state_type; }; template<typename _CharT, typename = char_traits<_CharT>> class basic_string_view { public: basic_string_view(const _CharT* ){}; }; using string_view = basic_string_view<char>; } # 3 "" 2 export module hello; export void greeter(std::string_view){} If we accept invalid test case this and main.cc can be further reduced into: - hello.cc module; # 1 "" 1 template <class> struct char_traits; typedef struct { } __mbstate_t; template <> struct char_traits<char> { __mbstate_t state_type; }; template <typename _CharT, typename = char_traits<_CharT>> class basic_string_view; using string_view = basic_string_view<char>; # 3 "" 2 export module hello; void greeter(string_view); - main.cc import hello; greeter Bisection points me to the following commit as the one fixing the bug: commit 47145e6916f58e1cd4f562c06fa7289da49f690c Author: Nathan Sidwell <nathan@acm.org> Date: Tue Feb 23 07:08:55 2021 -0800 c++: typedef for linkage [PR 99208] As this is the first time I use cvise, you probably want to double check those informations.
next prev parent reply other threads:[~2022-04-26 20:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-22 10:12 [Bug c++/98417] New: -internal compiler error when using -g patrick.kox at commandoregel dot be 2020-12-22 11:22 ` [Bug c++/98417] ICE when using C++ modules and -g marxin at gcc dot gnu.org 2021-01-18 6:57 ` boris at kolpackov dot net 2022-04-26 20:29 ` remi.galanalfonso at gmail dot com [this message] 2022-04-27 10:45 ` boris at kolpackov dot net 2024-02-11 14:23 ` nshead 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-98417-4-KvYlvVKkrx@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).