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++/95209] std::filesystem::path::lexically_normal mangles "//foo" Date: Thu, 21 May 2020 19:33:51 +0000 [thread overview] Message-ID: <bug-95209-4-SRHEWUOPNt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95209-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95209 --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to M Welinder from comment #4) > Sorry about the missing "-v". It is indeed a x86_64-suse-linux system. > (It's not internet facing or I'd go get the full output.) > > "Implementation defined", yes, but the implementation is the os, not the > compiler/library. No, that's wrong. "This document specifies requirements for implementations of the C ++ programming language." The OS is not an implementation of the C++ programming language. GCC is. > The OS gets to choose and, possibly, change its mind > long after the compiler has written its output. The OS gets to choose whether that path has any effect for system calls to t he OS, but it's the C++ implementation that chooses the definition of root-name in the std::filesystem library. > > What meaning does //foo have on linux? > > Today, nothing separate, tomorrow who knows? The OS is at perfect liberty > to assign a different meaning on Fridays if it so pleases. Run the linux > binary > on windows today and I suspect, but haven't verified, that it matters right > now. If you can verify that I'd be interested, but not in a suspicion. > Note that "cd //tmp" in bash shows that bash takes care not to mangle it.
prev parent reply other threads:[~2020-05-21 19:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-19 13:53 [Bug libstdc++/95209] New: " terra at gnome dot org 2020-05-19 13:55 ` [Bug libstdc++/95209] " terra at gnome dot org 2020-05-19 15:48 ` redi at gcc dot gnu.org 2020-05-21 12:26 ` redi at gcc dot gnu.org 2020-05-21 12:32 ` redi at gcc dot gnu.org 2020-05-21 16:59 ` terra at gnome dot org 2020-05-21 19:33 ` redi at gcc dot gnu.org [this message]
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-95209-4-SRHEWUOPNt@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).