public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi 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, 09 Apr 2021 17:00:56 +0000 [thread overview] Message-ID: <bug-92546-4-VuCie8P9l7@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 #23 from Jonathan Wakely <redi at gcc dot gnu.org> --- The other improvement we could make for C++20 is to replace <iterator> in <bits/ranges_algobase.h> with smaller pieces, as it doesn't need the definition of std::streambuf_iterator: --- a/libstdc++-v3/include/bits/ranges_algobase.h +++ b/libstdc++-v3/include/bits/ranges_algobase.h @@ -33,7 +33,10 @@ #if __cplusplus > 201703L #include <compare> -#include <iterator> +#include <bits/stl_iterator_base_types.h> +#include <bits/stl_iterator_base_funcs.h> +#include <bits/stl_iterator.h> +#include <bits/range_access.h> #include <bits/ranges_base.h> // ranges::begin, ranges::range etc. #include <bits/invoke.h> // __invoke #include <bits/cpp_type_traits.h> // __is_byte And <bits/streambuf_iterator> doesn't need <streambuf>, just <iosfwd>.
next prev parent reply other threads:[~2021-04-09 17:00 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 [this message] 2021-10-01 19:40 ` cvs-commit at gcc dot gnu.org 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-VuCie8P9l7@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: linkBe 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).