From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Tamar Christina <Tamar.Christina@arm.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/3] Move ftime to a compatibility symbol
Date: Mon, 19 Oct 2020 12:46:20 +0200 [thread overview]
Message-ID: <87tuuqa3yb.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <VI1PR08MB5325E174DFCD1DFACC80255DFF1E0@VI1PR08MB5325.eurprd08.prod.outlook.com> (Tamar Christina's message of "Mon, 19 Oct 2020 10:20:57 +0000")
* Tamar Christina:
>> Has SPEC ever fixed any standards violations? I don't have access to the SPEC
>> web site, so I don't know if they have released patches to fix conformance
>> bugs in benchmarks. (I recall several discussions about aliasing violations in
>> older benchmarks on the GCC lists.)
>
> They do, and have in the past, but while I can reasonably get one for
> SPEC2017, SPEC2006 is no longer maintained as far as I am aware.
Here they refused it for SPEC2017:
| q1. Will SPEC fix spec_qsort.c?
|
| a1. No. There are two reasons:
|
| That's the way it is in real life
| The module spec_qsort.c is based directly on the BSD version, as updated Thu Mar 5 17:17:11 2015 UTC in revision 279666: https://svnweb.freebsd.org/base/head/lib/libc/stdlib/qsort.c?revision=279666.
| No moving targets
| SPEC CPU®2017 has already been released. Once source code has been released for a benchmark, SPEC strongly prefers not to change the source code unless there are compelling portability reasons.
|
| Note, therefore, that the patch attached to GCC bug 83201 is not approved by SPEC and would not be allowed in a reportable run.
<https://www.spec.org/cpu2017/Docs/benchmarks/505.mcf_r.html>
> If the header was still there but empty I could do something at link
> time, but since it doesn't exist at all I have to provide my own local
> headers. Also if you have a list of interfaces glibc plans to remove
> we can also feed this on to them to avoid in the next SPEC release.
> https://www.spec.org/cpuv8/
There is no such list. There isn't even consensus among glibc
developers that it's necessary to provide a deprecation notice before
removal. Building with an appropriate version of _POSIX_SOURCE can help.
A good indicator is whether a function has been removed by POSIX.
Sometimes the manual pages also mark a function as obsolete. Usually,
that's sufficient reason to stay away from it. For ftime, this happened
some time before 2004.
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 10:46 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 [this message]
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=87tuuqa3yb.fsf@oldenburg2.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=Tamar.Christina@arm.com \
--cc=fweimer@redhat.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).