From: Florian Weimer <fweimer@redhat.com>
To: GNU C Library <libc-alpha@sourceware.org>,
"Gabriel F. T. Gomes" <gftg@linux.vnet.ibm.com>
Subject: Legacy _IO_* symbols and Flaot128 transition
Date: Fri, 29 Jun 2018 14:49:00 -0000 [thread overview]
Message-ID: <a3d90e92-832e-4ca3-987d-acaff7ff5093@redhat.com> (raw)
libio exports a bunch of symbols for historic reasons:
_IO_fprintf
_IO_printf
_IO_sprintf
_IO_sscanf
_IO_vfprintf
_IO_vfscanf
_IO_vsprintf
These aren't compat symbols yet, but will not be in installed headers
for glibc 2.28. Zack's cleanup patches only turns _IO_vfscanf into a
compat symbol (in âAdd __vfscanf_internal and __vfwscanf_internal with
flags arguments.â).
I think we should turn all of them into compat symbols and drop their
compatibility wrappers from nldbl_nonshared.a, and avoid adding
binary128 compatibility wrappers for them.
I can work on a patch if that would help.
Comments?
Thanks,
Florian
next reply other threads:[~2018-06-29 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 14:49 Florian Weimer [this message]
2018-06-29 15:26 ` Gabriel F. T. Gomes
2018-06-29 15:29 ` Florian Weimer
2018-06-29 17:15 ` Joseph Myers
2018-07-02 7:22 ` Florian Weimer
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=a3d90e92-832e-4ca3-987d-acaff7ff5093@redhat.com \
--to=fweimer@redhat.com \
--cc=gftg@linux.vnet.ibm.com \
--cc=libc-alpha@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: link
Be 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).