public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jasio.lpn at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99999] segmentation fault when declaring concept in module Date: Fri, 09 Apr 2021 14:38:13 +0000 [thread overview] Message-ID: <bug-99999-4-owjUx8QOBe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99999-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99999 Marcin Nowak <jasio.lpn at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jasio.lpn at gmail dot com --- Comment #1 from Marcin Nowak <jasio.lpn at gmail dot com> --- Hi I wanted to check some new stuff from C++20 so I've compiled GCC 11 form git and wrote some test app. GCC version: gcc version 11.0.1 20210407 (experimental) (GCC) This is the main.cpp file that I've created: #include <iostream> #include <string> import test; int main() { std::string str = "Hello"; std::cout << str << std::endl; return 0; } And this is the test.cpp: module; #include <type_traits> #include <string> export module test; template <typename T> concept IsStdString = std::is_same_v<T, std::string>; Command line: c++ -std=c++20 -fmodules-ts test.cpp main.cpp Compiler doesn't throw any error but when I'm trying to exec app it gives me an error: [1] 71397 segmentation fault (core dumped) ./a.out If I remove concept part from test.cpp or move it into main.cpp app is working fine. I think it's a bug but it's new stuff in language so maybe I don't understand something Best regards
next prev parent reply other threads:[~2021-04-09 14:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-09 14:30 [Bug c++/99999] New: " jasio.lpn at gmail dot com 2021-04-09 14:38 ` jasio.lpn at gmail dot com [this message] 2024-03-06 20:49 ` [Bug c++/99999] " ppalka 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-99999-4-owjUx8QOBe@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).