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 c++/99805] [9 Regression] filesystem::path::parent_path got a wrong path
Date: Thu, 08 Apr 2021 17:04:36 +0000	[thread overview]
Message-ID: <bug-99805-4-5o7VfoB7UH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99805-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99805

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |10.3.1, 11.0
            Summary|[9/10 Regression]           |[9 Regression]
                   |filesystem::path::parent_pa |filesystem::path::parent_pa
                   |th got a wrong path         |th got a wrong path

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 10.4 too.

  parent reply	other threads:[~2021-04-08 17:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  3:05 [Bug c++/99805] New: " drfeng08 at gmail dot com
2021-03-29 15:15 ` [Bug c++/99805] " redi at gcc dot gnu.org
2021-04-01  6:15 ` drfeng08 at gmail dot com
2021-04-01 18:02 ` redi at gcc dot gnu.org
2021-04-01 18:03 ` [Bug c++/99805] [9/10/11 Regression] " redi at gcc dot gnu.org
2021-04-01 20:46 ` redi at gcc dot gnu.org
2021-04-01 21:06 ` redi at gcc dot gnu.org
2021-04-07 15:40 ` cvs-commit at gcc dot gnu.org
2021-04-07 15:43 ` [Bug c++/99805] [9/10 " redi at gcc dot gnu.org
2021-04-08 17:00 ` cvs-commit at gcc dot gnu.org
2021-04-08 17:04 ` redi at gcc dot gnu.org [this message]
2021-04-19 11:31 ` [Bug c++/99805] [9 " cvs-commit at gcc dot gnu.org
2021-04-19 11:31 ` 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-99805-4-5o7VfoB7UH@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).