public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lksfbdij at 10mail dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug time/30701] getutxent misbehaves on 32-bit x86 when _TIME_BITS=64 Date: Mon, 06 May 2024 22:54:34 +0000 [thread overview] Message-ID: <bug-30701-131-s5MFPtHKwp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30701-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30701 --- Comment #8 from Robert West <lksfbdij at 10mail dot org> --- Is this change ABI compatible? I see following report in libabigail: ┌──────────────────────┐ │ ABI Break: libc.so.6 │ └──────────────────────┘ Functions changes summary: 0 Removed, 2 Changed (13 filtered out), 0 Added functions Variables changes summary: 0 Removed, 0 Changed, 0 Added variable 2 functions with some indirect sub-type change: [C] 'function utmp* __getutent()' at getutent.c:27:1 has some indirect sub-type changes: Please note that the exported symbol of this function is getutent@@GLIBC_2.0 return type changed: in pointed to type 'struct utmp' at utmp.h:58:1: type size hasn't changed 1 data member changes (1 filtered): type of 'long int ut_session' changed: entity changed from 'long int' to compatible type 'typedef int32_t' at stdint-intn.h:26:1 type name changed from 'long int' to 'int' type size hasn't changed [C] 'function void getutmp(const utmpx*, utmp*)' at getutmp.c:29:1 has some indirect sub-type changes: Please note that the symbol of this function is getutmp@@GLIBC_2.1.1 and it aliases symbol: getutmpx@@GLIBC_2.1.1 parameter 1 of type 'const utmpx*' has sub-type changes: in pointed to type 'const utmpx': in unqualified underlying type 'struct utmpx' at utmpx.h:55:1: type size hasn't changed 1 data member changes (1 filtered): type of 'long int ut_session' changed: entity changed from 'long int' to compatible type 'typedef __int32_t' at types.h:41:1 type name changed from 'long int' to 'int' type size hasn't changed -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-05-06 22:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-30 20:07 [Bug time/30701] New: " eggert at cs dot ucla.edu 2023-07-31 6:42 ` [Bug time/30701] " bruno at clisp dot org 2023-07-31 9:49 ` sam at gentoo dot org 2023-08-01 9:10 ` aurelien at aurel32 dot net 2023-08-01 14:19 ` jwilk at jwilk dot net 2023-08-05 18:27 ` eggert at cs dot ucla.edu 2023-08-14 13:12 ` bruno at clisp dot org 2023-08-14 13:20 ` bruno at clisp dot org 2024-04-09 7:17 ` fweimer at redhat dot com 2024-04-15 11:52 ` fweimer at redhat dot com 2024-05-03 7:29 ` fweimer at redhat dot com 2024-05-03 7:29 ` fweimer at redhat dot com 2024-05-06 22:54 ` lksfbdij at 10mail dot org [this message] 2024-05-06 23:36 ` fweimer at redhat dot com
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-30701-131-s5MFPtHKwp@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).