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 libstdc++/106852] Implement C++23 P2465R3 Standard Library Modules std and std.compat
Date: Wed, 12 Jun 2024 20:04:04 +0000 [thread overview]
Message-ID: <bug-106852-4-gsC7K2jFEL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106852-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106852
m.cencora at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m.cencora at gmail dot com
--- Comment #6 from m.cencora at gmail dot com ---
Created attachment 58415
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58415&action=edit
C++ std module working with gcc-15 20240609 snapshot
Attaching an updated version of std module implementation.
Still TODO:
1. #include <execution> - ICE + TBB code is not module friendly due to use of
anonymous namespaces in header-files (no bug report)
2. cannot export operator new/delete (bug #115446, regression)
Workarounds applied:
1. cannot export same function twice (bug #115445, regression)
2. cannot export type declared/aliased in different namespace (bug #114685,
affected are: vector, exception_ptr, lldiv_t, chrono::*_clock)
prev parent reply other threads:[~2024-06-12 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 14:00 [Bug libstdc++/106852] New: " redi at gcc dot gnu.org
2022-09-25 5:53 ` [Bug libstdc++/106852] " de34 at live dot cn
2022-10-25 17:50 ` ppalka at gcc dot gnu.org
2022-12-09 15:29 ` pinskia at gcc dot gnu.org
2023-08-10 21:43 ` redi at gcc dot gnu.org
2024-02-11 13:33 ` nshead at gcc dot gnu.org
2024-04-26 23:09 ` pinskia at gcc dot gnu.org
2024-05-13 12:55 ` boris at kolpackov dot net
2024-05-29 13:17 ` redi at gcc dot gnu.org
2024-06-01 1:32 ` nshead at gcc dot gnu.org
2024-06-12 20:04 ` m.cencora at gmail dot com [this message]
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-106852-4-gsC7K2jFEL@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).