public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jo.hiller+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110805] g++ crash on modules with exported class providing string constant with obscure content
Date: Tue, 01 Aug 2023 17:38:31 +0000	[thread overview]
Message-ID: <bug-110805-4-SsJZm9i6aD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110805-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jochen Hiller <jo.hiller+gcc at gmail dot com> ---
> Gcc's module support is still experimental.

Sure. Nevertheless reporting bugs may help to come from experimental to stable.

I mainly do prototype development using C++ modules with Clang 16, but trying
regularly to get it working with Gcc as well. On my list is as well to check
MSVC state of implementation.

  parent reply	other threads:[~2023-08-01 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 16:27 [Bug c++/110805] New: " jo.hiller+gcc at gmail dot com
2023-08-01 16:52 ` [Bug c++/110805] " jo.hiller+gcc at gmail dot com
2023-08-01 17:33 ` pinskia at gcc dot gnu.org
2023-08-01 17:38 ` jo.hiller+gcc at gmail dot com [this message]
2024-03-06 20:24 ` 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-110805-4-SsJZm9i6aD@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).