https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118158
--- Comment #6 from Davide Pesavento ---
(In reply to Andrew Pinski from comment #1)
> Do you have a testcase?
#include
#include
#include
#include
#include
#define SOCKET_NAME "/tmp/foo.sock"
int main()
{
int sock = ::socket(AF_UNIX,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118158
Bug ID: 118158
Summary: std::filesystem::equivalent unsupported on socket
files
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113250
Bug ID: 113250
Summary: std::filesystem::equivalent("", "/") should throw
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246
--- Comment #5 from Davide Pesavento ---
(In reply to Jonathan Wakely from comment #2)
> > If there are no leading elements of p that exist, should canonical() be
> > called with an empty path? or should it not be called at all?
>
> It makes no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246
--- Comment #1 from Davide Pesavento ---
Another interesting(?) behavior, when run from a non-existing (deleted) working
directory:
weakly_canonical("foo") returns "foo", while weakly_canonical("./foo") throws:
> terminate called after throwin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113246
Bug ID: 113246
Summary: Behavior of std::filesystem::weakly_canonical with
non-existing relative paths
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severit
