public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ryan.burn at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99569] New: segfault when running a module
Date: Fri, 12 Mar 2021 23:24:24 +0000	[thread overview]
Message-ID: <bug-99569-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99569
           Summary: segfault when running a module
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ryan.burn at gmail dot com
  Target Milestone: ---

Here's how to reproduce

// a-m.cc
module;

#include <string>

export module a;

export std::string do_a() {
        return "abc";
}

// main.cc
#include <iostream>

import a;

int main() {
        std::cout << do_a() << "\n";
        return 0;
}

If I then run

g++ -fmodules-ts -std=c++20 -c a-m.cc
g++ -fmodules-ts -std=c++20 -c main.cc
g++ *.o
./a.out

the program prints

abc
Segmentation fault

This is the version of gcc I used

root@15a43977d8e1:/t/strfunc# g++ --version
g++ (GCC) 11.0.1 20210311 (experimental)
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 23:24 ryan.burn at gmail dot com [this message]
2023-09-17 19:24 ` [Bug c++/99569] " pinskia at gcc dot gnu.org
2024-03-06 18:01 ` ppalka at gcc dot gnu.org
2024-03-06 18:05 ` ppalka at gcc dot gnu.org
2024-03-06 20:09 ` 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-99569-4@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).