public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/106308] New: Consider using statx(2) for std::filesystem
@ 2022-07-14 21:25 redi at gcc dot gnu.org
2024-01-06 2:08 ` [Bug libstdc++/106308] " pinskia at gcc dot gnu.org
2024-01-11 9:12 ` kmatsui at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2022-07-14 21:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106308
Bug ID: 106308
Summary: Consider using statx(2) for std::filesystem
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
Target: *-*-linux*
We don't need all the info that stat(2) provides.
Whenever we want to create a filesystem::file_status we only need st_mode. This
would speed up many operations that use filesystem::file_status or
filesystem::file_type.
filesystem::file_size only uses st_mode and st_size
filesystem::read_symlink only uses st_mode and st_size
filesystem::copy and filesystem::copy_file only use st_mode, st_dev, st_ino,
and st_size.
filesystem::equivalent only uses st_mode, st_dev, st_ino.
filesystem::last_write_time only uses st_mtim.
We never care about atim, ctim, uid, nlink, rdev, blocks, or blksize (although
maybe we should use blksize for filesystem::copy_file). Fetching those fields
for files on remote filesystems is wasteful.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libstdc++/106308] Consider using statx(2) for std::filesystem
2022-07-14 21:25 [Bug libstdc++/106308] New: Consider using statx(2) for std::filesystem redi at gcc dot gnu.org
@ 2024-01-06 2:08 ` pinskia at gcc dot gnu.org
2024-01-11 9:12 ` kmatsui at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-01-06 2:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106308
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2024-01-06
Status|UNCONFIRMED |NEW
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libstdc++/106308] Consider using statx(2) for std::filesystem
2022-07-14 21:25 [Bug libstdc++/106308] New: Consider using statx(2) for std::filesystem redi at gcc dot gnu.org
2024-01-06 2:08 ` [Bug libstdc++/106308] " pinskia at gcc dot gnu.org
@ 2024-01-11 9:12 ` kmatsui at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: kmatsui at gcc dot gnu.org @ 2024-01-11 9:12 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106308
Ken Matsui <kmatsui at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-01-11 9:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-14 21:25 [Bug libstdc++/106308] New: Consider using statx(2) for std::filesystem redi at gcc dot gnu.org
2024-01-06 2:08 ` [Bug libstdc++/106308] " pinskia at gcc dot gnu.org
2024-01-11 9:12 ` kmatsui at gcc dot gnu.org
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).