public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug libc/29657] New: Incorrect struct stat for 64-bit time on linux/generic platforms
@ 2022-10-07 0:24 jsm28 at gcc dot gnu.org
2022-10-07 13:07 ` [Bug libc/29657] " adhemerval.zanella at linaro dot org
2022-10-25 19:07 ` adhemerval.zanella at linaro dot org
0 siblings, 2 replies; 3+ messages in thread
From: jsm28 at gcc dot gnu.org @ 2022-10-07 0:24 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=29657
Bug ID: 29657
Summary: Incorrect struct stat for 64-bit time on linux/generic
platforms
Product: glibc
Version: 2.36
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: jsm28 at gcc dot gnu.org
CC: drepper.fsp at gmail dot com
Target Milestone: ---
Host: csky*-linux* nios2*-linux*
sysdeps/unix/sysv/linux/generic/bits/struct_stat.h is missing the conditionals
to use bits/struct_stat_time64_helper.h in the __USE_TIME_BITS64 case. This
means that platforms using linux/generic but with __TIMESIZE == 32 (i.e. csky
and nios2, I think) get the wrong version of struct stat for 64-bit time, since
the actual function implementations use struct __stat64_t64 which does use
bits/struct_stat_time64_helper.h, so the type declared in the installed headers
is inconsistent with the implementation.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug libc/29657] Incorrect struct stat for 64-bit time on linux/generic platforms 2022-10-07 0:24 [Bug libc/29657] New: Incorrect struct stat for 64-bit time on linux/generic platforms jsm28 at gcc dot gnu.org @ 2022-10-07 13:07 ` adhemerval.zanella at linaro dot org 2022-10-25 19:07 ` adhemerval.zanella at linaro dot org 1 sibling, 0 replies; 3+ messages in thread From: adhemerval.zanella at linaro dot org @ 2022-10-07 13:07 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=29657 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |adhemerval.zanella at linaro dot o | |rg CC| |adhemerval.zanella at linaro dot o | |rg -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/29657] Incorrect struct stat for 64-bit time on linux/generic platforms 2022-10-07 0:24 [Bug libc/29657] New: Incorrect struct stat for 64-bit time on linux/generic platforms jsm28 at gcc dot gnu.org 2022-10-07 13:07 ` [Bug libc/29657] " adhemerval.zanella at linaro dot org @ 2022-10-25 19:07 ` adhemerval.zanella at linaro dot org 1 sibling, 0 replies; 3+ messages in thread From: adhemerval.zanella at linaro dot org @ 2022-10-25 19:07 UTC (permalink / raw) To: glibc-bugs https://sourceware.org/bugzilla/show_bug.cgi?id=29657 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.37 Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- Fixed on 2.37. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-10-25 19:07 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-10-07 0:24 [Bug libc/29657] New: Incorrect struct stat for 64-bit time on linux/generic platforms jsm28 at gcc dot gnu.org 2022-10-07 13:07 ` [Bug libc/29657] " adhemerval.zanella at linaro dot org 2022-10-25 19:07 ` adhemerval.zanella at linaro dot 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).