[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.20.1603050930330.31711@monopod.intra.ispras.ru>
Date: Sat, 5 Mar 2016 09:35:21 +0300 (MSK)
From: Alexander Monakov <amonakov@...ras.ru>
To: musl@...ts.openwall.com
Subject: Re: [RFC PATCH] micro-optimize __procfdname
On Sat, 5 Mar 2016, Rich Felker wrote:
> I've thought about having libc.h define a macro simply named "hidden"
> for declaring things with hidden visibility; then files needing it
> could just include libc.h and do stuff like:
>
> hidden char *__procfdname_impl(...);
>
> This would be more a matter of de-uglification than abstraction. Does
> anyone particularly like or hate this idea?
I like it, with a further note that 'internal' would be more precise: a libc
does not hand off pointers to its internal functions to callers.
(well, 'internal' might be subtly broken in a toolchain due to zero real-world
use, but that's unlikely; it's probably handled exactly like 'hidden', and
does not help optimizers today)
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
