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++/98471] [11 Regression] libstdc++ fails to build with clang on windows because of filesystem bug Date: Thu, 14 Jan 2021 16:28:02 +0000 [thread overview] Message-ID: <bug-98471-4-fxdq12yNyr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98471-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98471 --- Comment #4 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:57a4f5e4eacfbbbd0ca5f1e3f946c27d63e2b533 commit r11-6676-g57a4f5e4eacfbbbd0ca5f1e3f946c27d63e2b533 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Jan 14 14:26:19 2021 +0000 libstdc++: Define function to throw filesystem_error [PR 98471] Fix ordering problem on Windows targets where filesystem_error was used before being defined. libstdc++-v3/ChangeLog: PR libstdc++/98471 * include/bits/fs_path.h (__throw_conversion_error): New function to throw or abort on character conversion errors. (__wstr_from_utf8): Move definition after filesystem_error has been defined. Use __throw_conversion_error. (path::_S_convert<_EcharT>): Use __throw_conversion_error. (path::_S_str_convert<_CharT, _Traits, _Allocator>): Likewise. (path::u8string): Likewise.
next prev parent reply other threads:[~2021-01-14 16:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-29 8:49 [Bug c++/98471] New: " unlvsur at live dot com 2020-12-29 10:18 ` [Bug libstdc++/98471] " redi at gcc dot gnu.org 2021-01-13 3:12 ` unlvsur at live dot com 2021-01-13 9:33 ` redi at gcc dot gnu.org 2021-01-13 10:12 ` unlvsur at live dot com 2021-01-14 16:27 ` [Bug libstdc++/98471] [11 Regression] " redi at gcc dot gnu.org 2021-01-14 16:28 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-14 16:28 ` redi at gcc dot gnu.org 2021-01-14 20:04 ` unlvsur at live dot com
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-98471-4-fxdq12yNyr@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).