From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/3] Move ftime to a compatibility symbol
Date: Mon, 19 Oct 2020 13:58:34 +0200 [thread overview]
Message-ID: <874kmqa0lx.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <87362a4eft.fsf@igel.home> (Andreas Schwab's message of "Mon, 19 Oct 2020 13:56:22 +0200")
* Andreas Schwab:
> On Okt 19 2020, Florian Weimer via Libc-alpha wrote:
>
>> * Adhemerval Zanella via Libc-alpha:
>>
>>> 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).
>>
>> Why doesn't this break the conformance tests for
>> -D_POSIX_C_SOURCE=200112L?
>>
>> Have we ever turned anything into a compatibility symbol that is
>> declared in a standard header?
>
> I think it should be handled the same way as gets.
Yes, that would make sense. No compatibility symbol then.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-10-19 11:58 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 ` [PATCH 2/3] Move ftime to a compatibility symbol Szabolcs Nagy via Libc-alpha
2020-10-19 8:17 ` 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 [this message]
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=874kmqa0lx.fsf@oldenburg2.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=schwab@linux-m68k.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).