[Bug libstdc++/118158] std::filesystem::equivalent unsupported on socket files

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #11 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
<r...@gcc.gnu.org>:

https://gcc.gnu.org/g:e346a33381df08988f2b1c1f09f1ba573bb1f80b

commit r13-9465-ge346a33381df08988f2b1c1f09f1ba573bb1f80b
Author: Jonathan Wakely <jwak...@redhat.com>
Date:   Mon Dec 30 13:08:41 2024 +0000

    libstdc++: Implement LWG 2937 for std::filesystem::equivalent [PR118158]

    Do not report an error for (is_other(s1) && is_other(s2)) as the
    standard originally said, nor for (is_other(s1) || is_other(s2)) as
    libstdc++ was doing. We can compare inode numbers for special files and
    so give sensible answers.

    libstdc++-v3/ChangeLog:

            PR libstdc++/118158
            * src/c++17/fs_ops.cc (fs::equivalent): Remove error reporting
            for is_other(s1) && is_other(s2) case, as per LWG 2937.
            * testsuite/27_io/filesystem/operations/pr118158.cc: New test.

    (cherry picked from commit 301a961ffd0567eece55ece42e80a7ba9e855ba0)