From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id A13BE386F02B; Tue, 21 Apr 2020 08:55:32 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A13BE386F02B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1587459332;
 bh=22e73BSCbviTiDxq0gK40PLqksR9vUPQHdIvOYrAtAs=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=QICfobhIYNzmybPUZGEQYMdJZHOmRKuQfvKnTqLjdJ+7bcbuQuHhEJ1T+92a1wgY4
 WwIn9zYHdVD1PysMV1D04OWsS5A7V955mne/ss/hVpaOh1dh2rcDGThVgevIbv1hnK
 1QVdm3ID7Aug9tCoGHcv+bZiySU8/RXvj9xysbws=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.3.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: keywords target_milestone
Message-ID: <bug-94681-4-EOEDs9Hq7K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94681-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94681-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2020 08:55:32 -0000

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

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 relea=
se
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.=