public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29657] New: Incorrect struct stat for 64-bit time on linux/generic platforms Date: Fri, 07 Oct 2022 00:24:22 +0000 [thread overview] Message-ID: <bug-29657-131@http.sourceware.org/bugzilla/> (raw) 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.
next reply other threads:[~2022-10-07 0:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-07 0:24 jsm28 at gcc dot gnu.org [this message] 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
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-29657-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).