public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114600] [14 Regression] [modules] redefinition errors when using certain std headers in GMF
Date: Wed, 24 Apr 2024 13:46:31 +0000	[thread overview]
Message-ID: <bug-114600-4-Hg6TkNfome@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114600-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to m.cencora from comment #10)
> Created attachment 57924 [details]
> Full "std' modules with workarounds
> 
> Here is an improved version of "std" module, with workarounds for:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114683
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114685

Interesting, thanks!

IIUC in light of these 'export using' bugs the most robust way to implement the
std module in GCC 14 is probably:

$ cat std.C
export module std;
export import <bits/stdc++.h>;

$ g++ -fmodules-ts -x c++-system-header bits/stdc++.h -x c++ std.C

This has the disadvantage of exposing implementation-detail entities and
requiring an additional step to build the <bits/stdc++.h> header module, but
should otherwise just work.

  parent reply	other threads:[~2024-04-24 13:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 10:07 [Bug c++/114600] New: " m.cencora at gmail dot com
2024-04-05 10:07 ` [Bug c++/114600] " m.cencora at gmail dot com
2024-04-05 12:55 ` [Bug c++/114600] [14 Regression] " ppalka at gcc dot gnu.org
2024-04-05 12:58 ` ppalka at gcc dot gnu.org
2024-04-05 13:10 ` nshead at gcc dot gnu.org
2024-04-05 13:33 ` ppalka at gcc dot gnu.org
2024-04-10 13:24 ` nshead at gcc dot gnu.org
2024-04-10 14:27 ` m.cencora at gmail dot com
2024-04-10 15:41 ` redi at gcc dot gnu.org
2024-04-10 20:55 ` m.cencora at gmail dot com
2024-04-10 21:03 ` m.cencora at gmail dot com
2024-04-15  8:26 ` cvs-commit at gcc dot gnu.org
2024-04-24 13:46 ` ppalka at gcc dot gnu.org [this message]
2024-04-24 13:50 ` 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-114600-4-Hg6TkNfome@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).