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: Thu, 17 Mar 2022 17:52:06 +0000 [thread overview] Message-ID: <bug-92546-4-VHwoFH5fOE@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 #26 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:00df7ee4474faca91d3460fe78a88e280c6c1126 commit r12-7691-g00df7ee4474faca91d3460fe78a88e280c6c1126 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Mar 17 14:36:07 2022 +0000 libstdc++: Avoid including <algorithm> in <filesystem> [PR92546] This only affects Windows, but reduces the preprocessed size of <filesystem> significantly. libstdc++-v3/ChangeLog: PR libstdc++/92546 * include/bits/fs_path.h (path::make_preferred): Use handwritten loop instead of std::replace.
next prev parent reply other threads:[~2022-03-17 17:52 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 2021-10-08 14:00 ` cvs-commit at gcc dot gnu.org 2022-03-17 17:52 ` cvs-commit at gcc dot gnu.org [this message] 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-VHwoFH5fOE@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).