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.
