public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/31776] __nldbl__IO_vfscanf should be a compat symbol Date: Thu, 23 May 2024 20:09:34 +0000 [thread overview] Message-ID: <bug-31776-131-A6f2l98k8o@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31776-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31776 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NOTABUG |--- --- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> --- There are #if SHLIB_COMPAT (libc, GLIBC_2_0, GLIBC_2_29) int attribute_compat_text_section __nldbl__IO_vfscanf (FILE *s, const char *fmt, va_list ap, int *errp) { int ret = __vfscanf_internal (s, fmt, ap, SCANF_LDBL_IS_DBL); if (__glibc_unlikely (errp != 0)) *errp = (ret == -1); return ret; } #endif and But __nldbl__IO_vfscanf isn't marked as a compat symbol and there are references to __nldbl__IO_vfscanf in libnldbl_nonshared.a. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-05-23 20:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-21 13:44 [Bug stdio/31776] New: " hjl.tools at gmail dot com 2024-05-21 14:10 ` [Bug stdio/31776] " schwab@linux-m68k.org 2024-05-21 18:07 ` fweimer at redhat dot com 2024-05-21 18:31 ` hjl.tools at gmail dot com 2024-05-23 20:09 ` hjl.tools at gmail dot com [this message] 2024-05-23 20:11 ` fweimer at redhat dot com 2024-05-24 15:05 ` hjl.tools at gmail dot com 2024-05-24 18:33 ` hjl.tools at gmail dot com 2024-07-02 9:19 ` 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-31776-131-A6f2l98k8o@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).