public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92546] Large increase in preprocessed file sizes in C++2a mode
Date: Fri, 01 Oct 2021 19:40:12 +0000 [thread overview]
Message-ID: <bug-92546-4-mgQbHCu1Cv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92546-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92546
--- Comment #24 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:acf3a21cbc26b39b73c0006300f35ff017ddd6cb
commit r12-4083-gacf3a21cbc26b39b73c0006300f35ff017ddd6cb
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Fri Oct 1 20:37:02 2021 +0100
libstdc++: Reduce header dependencies for C++20 std::erase [PR92546]
This reduces the preprocessed size of <deque>, <string> and <vector> by
not including <bits/stl_algo.h> for std::remove and std::remove_if.
Also unwrap iterators using __niter_base, to avoid redundant debug mode
checks.
PR libstdc++/92546
* include/bits/erase_if.h (__erase_nodes_if): Use __niter_base to
unwrap debug iterators.
* include/bits/refwrap.h: Do not error if included in C++03.
* include/bits/stl_algo.h (__remove_if): Move to ...
* include/bits/stl_algobase.h (__remove_if): ... here.
* include/std/deque (erase, erase_if): Use __remove_if instead of
remove and remove_if.
* include/std/string (erase, erase_if): Likewise.
* include/std/vector (erase, erase_if): Likewise.
next prev parent reply other threads:[~2021-10-01 19:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92546-4@http.gcc.gnu.org/bugzilla/>
2020-04-01 8:09 ` [Bug libstdc++/92546] [10 Regression] " rguenth at gcc dot gnu.org
2020-04-01 8:45 ` redi at gcc dot gnu.org
2020-05-07 11:56 ` [Bug libstdc++/92546] [10/11 " jakub at gcc dot gnu.org
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2020-11-05 0:02 ` redi at gcc dot gnu.org
2020-11-05 0:04 ` redi at gcc dot gnu.org
2020-11-19 13:36 ` cvs-commit at gcc dot gnu.org
2020-11-20 13:27 ` cvs-commit at gcc dot gnu.org
2020-11-20 13:49 ` cvs-commit at gcc dot gnu.org
2020-11-20 19:29 ` redi at gcc dot gnu.org
2020-12-13 22:02 ` redi at gcc dot gnu.org
2021-01-28 16:29 ` jakub at gcc dot gnu.org
2021-01-28 17:07 ` [Bug libstdc++/92546] " redi at gcc dot gnu.org
2021-04-08 8:47 ` redi at gcc dot gnu.org
2021-04-08 8:50 ` redi at gcc dot gnu.org
2021-04-08 8:51 ` redi at gcc dot gnu.org
2021-04-08 8:51 ` redi at gcc dot gnu.org
2021-04-09 17:00 ` redi at gcc dot gnu.org
2021-10-01 19:40 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-08 14:00 ` cvs-commit at gcc dot gnu.org
2022-03-17 17:52 ` cvs-commit at gcc dot gnu.org
2022-03-18 10:42 ` redi at gcc dot gnu.org
2022-03-18 10:46 ` cvs-commit at gcc dot gnu.org
2022-03-18 10:57 ` redi at gcc dot gnu.org
2022-03-18 11:00 ` redi at gcc dot gnu.org
2022-03-24 22:31 ` redi at gcc dot gnu.org
2022-05-06 8:30 ` jakub at gcc dot gnu.org
2023-05-08 12:21 ` rguenth at gcc dot gnu.org
2023-05-08 12:49 ` redi at gcc dot gnu.org
2023-05-12 14:47 ` redi 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-92546-4-mgQbHCu1Cv@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).