From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] libio: Remove _IO_adjust_column, _IO_adjust_wcolumn, column tracking
Date: Thu, 21 Apr 2022 12:00:08 +0200 [thread overview]
Message-ID: <87levyvjrr.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87pmlavjwv.fsf@oldenburg.str.redhat.com> (Florian Weimer's message of "Thu, 21 Apr 2022 11:57:04 +0200")
* Florian Weimer:
> Column number tracking was removed from the iostream library during
> C++98 standardization. It looks like it was never used by
> applications.
>
> On most ports, this is hard symbol removal (no compatibility symbol).
> However, for GLIBC_2.0 ports, it is necessary to keep an
> _IO_adjust_column export because old libstdc++ references this symbol,
> although after the column number is no longer updated by glibc,
> it will not be called anymore.
>
> _IO_adjust_wcolumn was never used in libstdc++. (The wide character
> support was not completed before the switch to C++98 <iostream> and
> its template-based implementation.)
>
> Tested on i686-linux-gnu and x86_64-linux-gnu. Built with
> build-many-glibcs.py.
And I forgot the NEWS entry:
diff --git a/NEWS b/NEWS
index 4b6d9de2b5..e04aa771f5 100644
--- a/NEWS
+++ b/NEWS
@@ -17,6 +17,12 @@ Deprecated and removed features, and other changes affecting compatibility:
removal of the LD_TRACE_PRELINKING, and LD_USE_LOAD_BIAS, environment
variables and their functionality in the dynamic loader.
+* Column number tracking for streams and the _IO_adjust_column and
+ _IO_adjust_wcolumn functions have been removed. For targets with the
+ GLIBC_2.0 symbol version, a compatibility definition of
+ _IO_adjust_column is still provided; otherwise the symbols have been
+ removed completely.
+
Changes to build and runtime requirements:
[Add changes to build and runtime requirements here]
Thanks,
Florian
prev parent reply other threads:[~2022-04-21 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 9:57 Florian Weimer
2022-04-21 10:00 ` Florian Weimer [this message]
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=87levyvjrr.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.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).