From: Joseph Myers <joseph@codesourcery.com>
To: Wilco Dijkstra <wdijkstr@arm.com>
Cc: <pinskia@gmail.com>, GNU C Library <libc-alpha@sourceware.org>
Subject: RE: [PATCH] Use strlen when searching for a nul char
Date: Wed, 07 Oct 2015 17:17:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1510071706290.29388@digraph.polyomino.org.uk> (raw)
In-Reply-To: <003c01d1011e$cda64e50$68f2eaf0$@com>
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
On Wed, 7 Oct 2015, Wilco Dijkstra wrote:
> > I agree; I'd rather discourage the addition of such optimizations as
> > inlines in glibc unless they depend on information that's inherently not
> > available to GCC (e.g. properties of architecture-specific function
> > implementations in glibc). As I said before in
> > <https://sourceware.org/ml/libc-alpha/2015-06/msg00146.html> the aim
> > should be to make the GNU system as a whole as good as possible.
>
> Does this mean we no longer care about supporting older GCC versions
> efficiently in GLIBC?
We expect people caring about microoptimizations to use current tool
versions.
> Ie. can we remove bits/string2.h and just do a trivial implementation of
> the inlines in string/string-inlines.c?
See the discussion starting at
<https://sourceware.org/ml/libc-alpha/2015-05/msg00526.html>. We could
remove optimizations only relevant to old compilers (say pre-4.1 or
pre-4.3, potentially pre-4.6 if that actually means significant cleanup),
yes.
Note this does *not* automatically mean completely removing the header -
for example, code mapping __func to __builtin_func may still be relevant,
at least when building glibc, so you need to be careful that the code you
remove really is dead with modern GCC. And you need to allow for the x86
version of string-inlines.c as well. See my reviews of Ondøej's patches
<https://sourceware.org/ml/libc-alpha/2015-05/msg00770.html> and
<https://sourceware.org/ml/libc-alpha/2015-05/msg00772.html>.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-10-07 17:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 14:30 Wilco Dijkstra
2015-10-07 14:46 ` pinskia
2015-10-07 14:50 ` Wilco Dijkstra
2015-10-07 15:20 ` Joseph Myers
2015-10-07 15:30 ` Andreas Schwab
2015-10-07 16:40 ` Wilco Dijkstra
2015-10-07 17:17 ` Joseph Myers [this message]
2016-02-25 13:10 Wilco Dijkstra
2016-04-15 12:36 ` Wilco Dijkstra
2016-04-19 17:57 ` Mike Frysinger
2016-04-19 20:27 ` Adhemerval Zanella
2016-04-19 20:51 ` Mike Frysinger
2016-04-19 21:01 ` Adhemerval Zanella
2016-04-19 21:23 ` Mike Frysinger
2016-04-19 22:03 ` Wilco Dijkstra
2016-04-19 22:21 ` Mike Frysinger
2016-04-20 14:50 ` Wilco Dijkstra
2016-04-20 15:24 ` Mike Frysinger
2016-04-20 15:53 ` Wilco Dijkstra
2016-05-12 14:05 ` Wilco Dijkstra
2016-06-03 12:38 ` Wilco Dijkstra
2016-06-21 13:37 ` Wilco Dijkstra
2016-04-20 15:31 ` Wilco Dijkstra
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=alpine.DEB.2.10.1510071706290.29388@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=pinskia@gmail.com \
--cc=wdijkstr@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).