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++/94681] filesystem::sysmlink_status using stat instead of lstat when --disable-libstdcxx-filesystem-ts
Date: Tue, 21 Apr 2020 08:55:32 +0000	[thread overview]
Message-ID: <bug-94681-4-EOEDs9Hq7K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94681-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch
   Target Milestone|---                         |9.4

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm not too concerned about the impact on people using the --disable option,
because the default for most targets is to enable it, and everything works.

But for systems where the default is --disable it means the std::filesystem
support is borked.

I think it's a bit too late to fix this for GCC 10.1 because it would enable
new code paths on systems where --disable is the default, and those are the
less well-tested targets. I don't want to break those right before we release
GCC 10.

So I'll fix this on master as soon as GCC 10.1 is released, and backport it for
10.2 and 9.4 later.

  parent reply	other threads:[~2020-04-21  8:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  8:41 [Bug libstdc++/94681] New: " valentin.david at codethink dot co.uk
2020-04-21  8:42 ` [Bug libstdc++/94681] " redi at gcc dot gnu.org
2020-04-21  8:55 ` redi at gcc dot gnu.org [this message]
2020-08-10 12:22 ` cvs-commit at gcc dot gnu.org
2020-08-10 12:25 ` redi at gcc dot gnu.org
2020-08-10 14:37 ` clyon at gcc dot gnu.org
2020-08-10 16:04 ` redi at gcc dot gnu.org
2020-08-10 18:12 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:00 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:00 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:14 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:14 ` cvs-commit at gcc dot gnu.org
2020-09-21 23:14 ` redi at gcc dot gnu.org
2020-09-21 23:14 ` 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-94681-4-EOEDs9Hq7K@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).