public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "m.cencora at gmail dot com" <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, 10 Apr 2024 14:27:33 +0000	[thread overview]
Message-ID: <bug-114600-4-cMEOghdCqd@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 #7 from m.cencora at gmail dot com ---
Created attachment 57921
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57921&action=edit
Full "std" module

FYI if you want to stress test the modules impl w.r.t. similar issues, here is
std.cpp for almost whole Standard Library.

Some code is disabled (with 'bug' comment).

This is based on semi-preprocessed and hand-adjusted 'std' module code from
libc++

  parent reply	other threads:[~2024-04-10 14:27 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 [this message]
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
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-cMEOghdCqd@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).