From: Szabolcs Nagy via Libc-alpha <libc-alpha@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/3] Move ftime to a compatibility symbol
Date: Mon, 19 Oct 2020 08:55:19 +0100 [thread overview]
Message-ID: <20201019075518.GJ3819@arm.com> (raw)
In-Reply-To: <20201015130632.90961-2-adhemerval.zanella@linaro.org>
The 10/15/2020 10:06, Adhemerval Zanella via Libc-alpha wrote:
> It was made deprecated on 2.31, so it moves to compat symbol after
> two releases. It was also removed from exported symbol for riscv32
> (since ABI will be supported on for 2.33).
>
> Checked on x86_64-linux-gnu and i686-linux-gnu.
> ---
> include/sys/timeb.h | 1 -
> .../unix/sysv/linux/riscv/rv32/libc.abilist | 1 -
> time/Makefile | 5 +-
> time/ftime.c | 19 +++++-
> time/sys/timeb.h | 44 --------------
> time/tst-ftime.c | 59 ++++++++++---------
> 6 files changed, 50 insertions(+), 79 deletions(-)
> delete mode 100644 include/sys/timeb.h
> delete mode 100644 time/sys/timeb.h
removing sys/timeb.h and ftime breaks several
spec2006 and spec2017 benchmarks.
which means this header is used in practice,
sometimes without configure checks.
is there a reason it cannot be supported?
next prev parent reply other threads:[~2020-10-19 7:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 13:06 [PATCH 1/3] linux: Fix time64 support for futimesat Adhemerval Zanella via Libc-alpha
2020-10-15 13:06 ` [PATCH 2/3] Move ftime to a compatibility symbol Adhemerval Zanella via Libc-alpha
2020-10-16 9:05 ` Lukasz Majewski
2020-10-16 18:18 ` [COMMITTED] Add NEWS entry for ftime compatibility move Adhemerval Zanella via Libc-alpha
2020-10-19 7:55 ` Szabolcs Nagy via Libc-alpha [this message]
2020-10-19 8:17 ` [PATCH 2/3] Move ftime to a compatibility symbol Andreas Schwab
2020-10-19 8:30 ` Florian Weimer via Libc-alpha
2020-10-19 9:18 ` Tamar Christina via Libc-alpha
2020-10-19 9:51 ` Florian Weimer via Libc-alpha
2020-10-19 10:20 ` Tamar Christina via Libc-alpha
2020-10-19 10:46 ` Florian Weimer via Libc-alpha
2020-10-19 10:49 ` Florian Weimer via Libc-alpha
2020-10-19 11:56 ` Andreas Schwab
2020-10-19 11:58 ` Florian Weimer via Libc-alpha
2020-10-19 12:30 ` Adhemerval Zanella via Libc-alpha
2020-10-19 12:31 ` Adhemerval Zanella via Libc-alpha
2020-10-19 17:56 ` Joseph Myers
2020-10-15 13:06 ` [PATCH 3/3] linux: Add 64-bit time_t support for wait3 Adhemerval Zanella via Libc-alpha
2020-10-15 14:43 ` Alistair Francis via Libc-alpha
2020-10-16 9:14 ` Lukasz Majewski
2020-10-16 17:02 ` Adhemerval Zanella via Libc-alpha
2020-10-18 19:55 ` Lukasz Majewski
2020-10-16 8:41 ` [PATCH 1/3] linux: Fix time64 support for futimesat Lukasz Majewski
2020-10-16 14:20 ` Adhemerval Zanella via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201019075518.GJ3819@arm.com \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=szabolcs.nagy@arm.com \
/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).